On Wed, Jun 07, 2017 at 07:51:55AM +, Liu, Yi L wrote:
> Hi Peter,
>
> Some updates on it.
>
> > -Original Message-
> > From: Peter Xu [mailto:pet...@redhat.com]
> > Sent: Thursday, April 27, 2017 5:34 PM
> > To: qemu-devel@nongnu.org
> > Cc: Lan, Tianyu ; Paolo Bonzini ;
> > Tian, Ke
Hi Peter,
Some updates on it.
> -Original Message-
> From: Peter Xu [mailto:pet...@redhat.com]
> Sent: Thursday, April 27, 2017 5:34 PM
> To: qemu-devel@nongnu.org
> Cc: Lan, Tianyu ; Paolo Bonzini ;
> Tian, Kevin ; Liu, Yi L ;
> pet...@redhat.com; Jason Wang ; David Gibson
> ; Alex Willi
On Fri, Apr 28, 2017 at 06:01:58PM +0800, Liu, Yi L wrote:
> On Thu, Apr 27, 2017 at 05:34:20PM +0800, Peter Xu wrote:
> > Time to consider a common stuff for IOMMU. Let's start from an common
> > IOMMU object (which should be inlayed in custom IOMMU implementations)
> > and a notifier mechanism.
>
On Thu, Apr 27, 2017 at 05:34:20PM +0800, Peter Xu wrote:
> Time to consider a common stuff for IOMMU. Let's start from an common
> IOMMU object (which should be inlayed in custom IOMMU implementations)
> and a notifier mechanism.
>
> Let VT-d IOMMU be the first user.
>
> An example to use this p
Time to consider a common stuff for IOMMU. Let's start from an common
IOMMU object (which should be inlayed in custom IOMMU implementations)
and a notifier mechanism.
Let VT-d IOMMU be the first user.
An example to use this per-iommu notifier:
(when registering)
iommu = address_space_iommu_g
