On Fri, Jan 15, 2021 at 05:43:35PM +0530, Vivek Gautam wrote: > aisd_bits data is required to prepare stage-1 tables for arm-smmu-v3. > > Signed-off-by: Vivek Gautam <[email protected]> > Cc: Joerg Roedel <[email protected]> > Cc: Will Deacon <[email protected]> > Cc: Robin Murphy <[email protected]> > Cc: Jean-Philippe Brucker <[email protected]> > Cc: Eric Auger <[email protected]> > Cc: Alex Williamson <[email protected]> > Cc: Kevin Tian <[email protected]> > Cc: Jacob Pan <[email protected]> > Cc: Liu Yi L <[email protected]> > Cc: Lorenzo Pieralisi <[email protected]> > Cc: Shameerali Kolothum Thodi <[email protected]> > --- > include/uapi/linux/iommu.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/include/uapi/linux/iommu.h b/include/uapi/linux/iommu.h > index 082d758dd016..96abbfc7c643 100644 > --- a/include/uapi/linux/iommu.h > +++ b/include/uapi/linux/iommu.h > @@ -357,7 +357,7 @@ struct iommu_pasid_smmuv3 { > __u32 version; > __u8 s1fmt; > __u8 s1dss; > - __u8 padding[2]; > + __u16 asid_bits;
Is this used anywhere? This struct is passed from host userspace to host kernel to attach the PASID table, so I don't think it needs an asid_bits field. Thanks, Jean
