[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DS0PR11MB752907DDEBA69BFD823F09EBC305A@DS0PR11MB7529.namprd11.prod.outlook.com>
Date: Mon, 31 Jul 2023 12:44:25 +0000
From: "Liu, Yi L" <yi.l.liu@...el.com>
To: Jason Gunthorpe <jgg@...dia.com>,
"Tian, Kevin" <kevin.tian@...el.com>
CC: "joro@...tes.org" <joro@...tes.org>,
"alex.williamson@...hat.com" <alex.williamson@...hat.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>,
"nicolinc@...dia.com" <nicolinc@...dia.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 v3 01/17] iommu: Add new iommu op to create domains owned
by userspace
> From: Jason Gunthorpe <jgg@...dia.com>
> Sent: Saturday, July 29, 2023 12:56 AM
>
> On Fri, Jul 28, 2023 at 09:37:21AM +0000, Tian, Kevin wrote:
> > > From: Yi Liu <yi.l.liu@...el.com>
> > > Sent: Monday, July 24, 2023 7:04 PM
> > >
> > > + * @domain_alloc_user: allocate a user iommu domain corresponding to
> > > the input
> > > + * @hwpt_type that is defined as enum iommu_hwpt_type in the
> > > + * include/uapi/linux/iommufd.h. A returning domain will be
> > > + * set to an IOMMU_DOMAIN_NESTED type, upon valid
> > > @user_data
> > > + * and @parent that is a kernel-managed domain. Otherwise,
> > > + * it will be set to an IOMMU_DOMAIN_UNMANAGED type.
> > > Return
> > > + * ERR_PTR on allocation failure.
> >
> > "If @user_data is valid and @parent points to a kernel-managed domain,
> > the returning domain is set to IOMMU_DOMAIN_NESTED type. Otherwise
> > it is set to IOMMU_DOMAIN_UNMANAGED type."
>
> "If @user_data is valid and @parent points to a kernel-managed domain,
> then the returned domain must be the IOMMU_DOMAIN_NESTED type. Otherwise
> the returned domain is IOMMU_DOMAIN_UNMANAGED."
>
> Notice the detail that this API expects the driver to set the type and
> fully initialize the domain, including the generic iommu_domain
> struct, which is different than alloc_domain.
>
> When we implement this in drivers we should tidy this so all the alloc
> flows fully initialize the domain internally.
Yes. this should be documented in the kdoc. Is it?
Regards,
Yi Liu
Powered by blists - more mailing lists