[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BN9PR11MB52767F29A6C11157659D375B8C12A@BN9PR11MB5276.namprd11.prod.outlook.com>
Date: Wed, 9 Aug 2023 09:49:16 +0000
From: "Tian, Kevin" <kevin.tian@...el.com>
To: Baolu Lu <baolu.lu@...ux.intel.com>,
"Zhang, Tina" <tina.zhang@...el.com>,
Jason Gunthorpe <jgg@...pe.ca>,
Michael Shavit <mshavit@...gle.com>
CC: "iommu@...ts.linux.dev" <iommu@...ts.linux.dev>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 2/5] iommu: Call helper function to get assigned pasid
value
> From: Baolu Lu <baolu.lu@...ux.intel.com>
> Sent: Wednesday, August 9, 2023 8:22 AM
>
> On 2023/8/8 15:49, Tina Zhang wrote:
> > Use the helper function mm_get_pasid() to get the mm assigned pasid
> > value.
>
> For internal iommu drivers, perhaps we should use another helper.
> Something like sva_domain_get_pasid()?
>
> Suppose that the iommu drivers should have no idea about the "mm".
>
Aren't all touched functions accept a struct mm_struct pointer?
Powered by blists - more mailing lists