Re: [Xen-devel] Xen virtual IOMMU high level design doc

[Paul Durrant <Paul.Durrant@xxxxxxxxxx>]

> -----Original Message-----
> From: Xen-devel [mailto:xen-devel-bounces@xxxxxxxxxxxxx] On Behalf Of
> Lan, Tianyu
> Sent: 17 August 2016 13:06
> To: Jan Beulich; Kevin Tian; Andrew Cooper; yang.zhang.wz@xxxxxxxxx; Jun
> Nakajima; Stefano Stabellini
> Cc: Anthony Perard; xuquan8@xxxxxxxxxx; xen-
> devel@xxxxxxxxxxxxxxxxxxx; Ian Jackson; Roger Pau Monne
> Subject: [Xen-devel] Xen virtual IOMMU high level design doc
> 
> Hi All:
>       The following is our Xen vIOMMU high level design for detail
> discussion. Please have a look. Very appreciate for your comments.
> This design doesn't cover changes when root port is moved to hypervisor.
> We may design it later.
> 
> 
> Content:
> ==========================================================
> =====================
> 1. Motivation of vIOMMU
>       1.1 Enable more than 255 vcpus
>       1.2 Support VFIO-based user space driver
>       1.3 Support guest Shared Virtual Memory (SVM)
> 2. Xen vIOMMU Architecture
>       2.1 2th level translation overview
>       2.2 Interrupt remapping overview
> 3. Xen hypervisor
>       3.1 New vIOMMU hypercall interface

Would it not have been better to build on the previously discussed (and mostly 
agreed) PV IOMMU interface? (See 
https://lists.xenproject.org/archives/html/xen-devel/2016-02/msg01428.html). An 
RFC implementation series was also posted 
(https://lists.xenproject.org/archives/html/xen-devel/2016-02/msg01441.html).

  Paul
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel