Re: [XEN RFC PATCH v5 3/5] xen/public: Introduce PV-IOMMU hypercall interface

2025-02-04 Thread Stefano Stabellini
On Tue, 4 Feb 2025, Teddy Astie wrote: > Hello Stefano, > > Le 03/02/2025 à 18:47, Stefano Stabellini a écrit : > > On Mon, 3 Feb 2025, Teddy Astie wrote: > >> Hello Jason, > >> > >> Le 30/01/2025 à 21:17, Jason Andryuk a écrit : > >>> Hi Teddy, > >>> > >>> Thanks for working on this.  I'm curious

Re: [XEN RFC PATCH v5 3/5] xen/public: Introduce PV-IOMMU hypercall interface

2025-02-04 Thread Julien Grall
Hi Stefano, On Tue, 4 Feb 2025 at 17:57, Stefano Stabellini wrote: > On Tue, 4 Feb 2025, Julien Grall wrote: > > On Tue, 4 Feb 2025 at 11:46, Teddy Astie wrote: > > If the hardware supports it, there is a alternative (still being > > drafted) interface to allow the guest to directl

Re: [XEN RFC PATCH v5 3/5] xen/public: Introduce PV-IOMMU hypercall interface

2025-02-04 Thread Stefano Stabellini
On Tue, 4 Feb 2025, Julien Grall wrote: > On Tue, 4 Feb 2025 at 11:46, Teddy Astie wrote: > If the hardware supports it, there is a alternative (still being > drafted) interface to allow the guest to directly provide native > pagetables. > > This is exposed through the "_nested

Re: [XEN RFC PATCH v5 3/5] xen/public: Introduce PV-IOMMU hypercall interface

2025-02-04 Thread Julien Grall
On Tue, 4 Feb 2025 at 11:46, Teddy Astie wrote: > If the hardware supports it, there is a alternative (still being > drafted) interface to allow the guest to directly provide native > pagetables. > > This is exposed through the "_nested" subcommands, there is no > implementation of this feature i

Re: [XEN RFC PATCH v5 3/5] xen/public: Introduce PV-IOMMU hypercall interface

2025-02-04 Thread Teddy Astie
Hello Stefano, Le 03/02/2025 à 18:47, Stefano Stabellini a écrit : > On Mon, 3 Feb 2025, Teddy Astie wrote: >> Hello Jason, >> >> Le 30/01/2025 à 21:17, Jason Andryuk a écrit : >>> Hi Teddy, >>> >>> Thanks for working on this.  I'm curious about your plans for this: >>> >>> On 2025-01-21 11:13, Te

Re: [XEN RFC PATCH v5 3/5] xen/public: Introduce PV-IOMMU hypercall interface

2025-02-03 Thread Stefano Stabellini
On Mon, 3 Feb 2025, Teddy Astie wrote: > Hello Jason, > > Le 30/01/2025 à 21:17, Jason Andryuk a écrit : > > Hi Teddy, > > > > Thanks for working on this.  I'm curious about your plans for this: > > > > On 2025-01-21 11:13, Teddy Astie wrote: > >> +/** > >> + * IOMMU_alloc_nested > >> + * Create a

Re: [XEN RFC PATCH v5 3/5] xen/public: Introduce PV-IOMMU hypercall interface

2025-02-03 Thread Teddy Astie
Hello Jason, Le 30/01/2025 à 21:17, Jason Andryuk a écrit : > Hi Teddy, > > Thanks for working on this.  I'm curious about your plans for this: > > On 2025-01-21 11:13, Teddy Astie wrote: >> +/** >> + * IOMMU_alloc_nested >> + * Create a nested IOMMU context (needs IOMMUCAP_nested). >> + * >> + *

Re: [XEN RFC PATCH v5 3/5] xen/public: Introduce PV-IOMMU hypercall interface

2025-01-30 Thread Jan Beulich
On 30.01.2025 21:17, Jason Andryuk wrote: > On 2025-01-21 11:13, Teddy Astie wrote: >> +/** >> + * IOMMU_alloc_nested >> + * Create a nested IOMMU context (needs IOMMUCAP_nested). >> + * >> + * This context uses a platform-specific page table from domain address >> space >> + * specified in pgtabl

Re: [XEN RFC PATCH v5 3/5] xen/public: Introduce PV-IOMMU hypercall interface

2025-01-30 Thread Jason Andryuk
Hi Teddy, Thanks for working on this. I'm curious about your plans for this: On 2025-01-21 11:13, Teddy Astie wrote: +/** + * IOMMU_alloc_nested + * Create a nested IOMMU context (needs IOMMUCAP_nested). + * + * This context uses a platform-specific page table from domain address space + * spe