[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241011163301.GQ762027@ziepe.ca>
Date: Fri, 11 Oct 2024 13:33:01 -0300
From: Jason Gunthorpe <jgg@...pe.ca>
To: Lu Baolu <baolu.lu@...ux.intel.com>
Cc: iommu@...ts.linux.dev, Joerg Roedel <joro@...tes.org>,
Will Deacon <will@...nel.org>, Robin Murphy <robin.murphy@....com>,
Kevin Tian <kevin.tian@...el.com>, Yi Liu <yi.l.liu@...el.com>,
Vasant Hegde <vasant.hegde@....com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/7] iommu/vt-d: Add domain_alloc_paging support
On Fri, Oct 11, 2024 at 10:22:52AM -0300, Jason Gunthorpe wrote:
> On Fri, Oct 11, 2024 at 12:27:16PM +0800, Lu Baolu wrote:
>
> > +static struct iommu_domain *intel_iommu_domain_alloc_paging(struct device *dev)
> > +{
> > + struct dmar_domain *dmar_domain;
> > + bool first_stage;
> > +
> > + first_stage = first_level_by_default(0);
> > + dmar_domain = paging_domain_alloc(dev, first_stage);
> > + if (IS_ERR(dmar_domain))
> > + return ERR_CAST(dmar_domain);
> > +
> > + return &dmar_domain->domain;
> > +}
>
> With the direction that Vasant's series is going in, I think this
> should be skipped and instead your other patch to make
> domain_alloc_user (which we will rename) a full functional replacement
> is the right thing.
Though I guess for patch ordering purposes it makes sense to just
leave this and remove it the next cycle
Jason
Powered by blists - more mailing lists