RE: [PATCH v5 04/15] vfio/type1: Report iommu nesting info to userspace

Hi Eric, > From: Auger Eric > Sent: Monday, July 20, 2020 4:33 PM > > Yi, > > On 7/20/20 9:51 AM, Liu, Yi L wrote: > > Hi Eric, > > > >> From: Auger Eric > >> Sent: Saturday, July 18, 2020 1:34 AM > >> > >> Yi, > >> > >> On 7/12/20 1:20 PM, Liu Yi L wrote: > >>> This patch exports iommu

Re: [PATCH v5 04/15] vfio/type1: Report iommu nesting info to userspace

Yi, On 7/20/20 9:51 AM, Liu, Yi L wrote: > Hi Eric, > >> From: Auger Eric >> Sent: Saturday, July 18, 2020 1:34 AM >> >> Yi, >> >> On 7/12/20 1:20 PM, Liu Yi L wrote: >>> This patch exports iommu nesting capability info to user space through >>> VFIO. User space is expected to check this info

RE: [PATCH v5 04/15] vfio/type1: Report iommu nesting info to userspace

Hi Eric, > From: Auger Eric > Sent: Saturday, July 18, 2020 1:34 AM > > Yi, > > On 7/12/20 1:20 PM, Liu Yi L wrote: > > This patch exports iommu nesting capability info to user space through > > VFIO. User space is expected to check this info for supported uAPIs (e.g. > it is not only to check

Re: [PATCH v5 04/15] vfio/type1: Report iommu nesting info to userspace

Yi, On 7/12/20 1:20 PM, Liu Yi L wrote: > This patch exports iommu nesting capability info to user space through > VFIO. User space is expected to check this info for supported uAPIs (e.g. it is not only to check the supported uAPIS but rather to know which callbacks it must call upon vIOMMU

[PATCH v5 04/15] vfio/type1: Report iommu nesting info to userspace

This patch exports iommu nesting capability info to user space through VFIO. User space is expected to check this info for supported uAPIs (e.g. PASID alloc/free, bind page table, and cache invalidation) and the vendor specific format information for first level/stage page table that will be bound