Hi Jacob, On 4/24/19 1:31 AM, Jacob Pan wrote: > To convert to/from cache types and granularities between generic and > VT-d specific counterparts, a 2D arrary is used. Introduce the limits array > to help define the converstion array size. conversion > > Signed-off-by: Jacob Pan <[email protected]> > --- > include/uapi/linux/iommu.h | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/include/uapi/linux/iommu.h b/include/uapi/linux/iommu.h > index 5c95905..2d8fac8 100644 > --- a/include/uapi/linux/iommu.h > +++ b/include/uapi/linux/iommu.h > @@ -197,6 +197,7 @@ struct iommu_inv_addr_info { > __u64 granule_size; > __u64 nb_granules; > }; > +#define NR_IOMMU_CACHE_INVAL_GRANU (3) > > /** > * First level/stage invalidation information > @@ -235,6 +236,7 @@ struct iommu_cache_invalidate_info { > struct iommu_inv_addr_info addr_info; > }; > }; > +#define NR_IOMMU_CACHE_TYPE (3) > /** > * struct gpasid_bind_data - Information about device and guest PASID binding > * @gcr3: Guest CR3 value from guest mm > Is it really something that needs to be exposed in the uapi?
Thanks Eric _______________________________________________ iommu mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/iommu
