[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BN9PR11MB527698FFB2960DE4424CBD4E8C419@BN9PR11MB5276.namprd11.prod.outlook.com>
Date: Wed, 24 May 2023 05:04:03 +0000
From: "Tian, Kevin" <kevin.tian@...el.com>
To: Nicolin Chen <nicolinc@...dia.com>
CC: "Liu, Yi L" <yi.l.liu@...el.com>,
"joro@...tes.org" <joro@...tes.org>,
"alex.williamson@...hat.com" <alex.williamson@...hat.com>,
"jgg@...dia.com" <jgg@...dia.com>,
"robin.murphy@....com" <robin.murphy@....com>,
"baolu.lu@...ux.intel.com" <baolu.lu@...ux.intel.com>,
"cohuck@...hat.com" <cohuck@...hat.com>,
"eric.auger@...hat.com" <eric.auger@...hat.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"mjrosato@...ux.ibm.com" <mjrosato@...ux.ibm.com>,
"chao.p.peng@...ux.intel.com" <chao.p.peng@...ux.intel.com>,
"yi.y.sun@...ux.intel.com" <yi.y.sun@...ux.intel.com>,
"peterx@...hat.com" <peterx@...hat.com>,
"jasowang@...hat.com" <jasowang@...hat.com>,
"shameerali.kolothum.thodi@...wei.com"
<shameerali.kolothum.thodi@...wei.com>,
"lulu@...hat.com" <lulu@...hat.com>,
"suravee.suthikulpanit@....com" <suravee.suthikulpanit@....com>,
"iommu@...ts.linux.dev" <iommu@...ts.linux.dev>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-kselftest@...r.kernel.org" <linux-kselftest@...r.kernel.org>,
"Duan, Zhenzhong" <zhenzhong.duan@...el.com>
Subject: RE: [PATCH v2 03/11] iommufd/hw_pagetable: Use domain_alloc_user op
for domain allocation
> From: Nicolin Chen <nicolinc@...dia.com>
> Sent: Saturday, May 20, 2023 2:58 AM
>
> On Fri, May 19, 2023 at 08:56:25AM +0000, Tian, Kevin wrote:
>
> > > From: Yi Liu <yi.l.liu@...el.com>
> > > Sent: Thursday, May 11, 2023 10:39 PM
> > >
> > >
> > > @@ -88,7 +90,10 @@ iommufd_hw_pagetable_alloc(struct iommufd_ctx
> > > *ictx, struct iommufd_ioas *ioas,
> > > refcount_inc(&ioas->obj.users);
> > > hwpt->ioas = ioas;
> > >
> > > - hwpt->domain = iommu_domain_alloc(idev->dev->bus);
> > > + if (ops->domain_alloc_user)
> > > + hwpt->domain = ops->domain_alloc_user(idev->dev, NULL,
> > > NULL);
> > > + else
> > > + hwpt->domain = iommu_domain_alloc(idev->dev->bus);
> >
> > this reminds the comment for @domain_alloc_user() should clarify
> > that UNMANGED domain type is assumed when no user data is
> > provided, to be compatible with iommu_domain_alloc().
>
> Yes. Perhaps:
>
> * @domain_alloc_user: allocate user iommu domain. A valid user_data
> pointer and
> * a parent pointer to a kernel-managed domain are required
> * to allocate an IOMMU_DOMAIN_NESTED domain. Otherwise,
> the
> * new domain will be set to an IOMMU_DOMAIN_UNMANAGED
> type.
>
yes, this is clearer.
Powered by blists - more mailing lists