From: Jason Gunthorpe <jgg@nvidia.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: Jacob Pan <jacob.jun.pan@linux.intel.com>,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
Lu Baolu <baolu.lu@linux.intel.com>,
Joerg Roedel <joro@8bytes.org>,
Jean-Philippe Brucker <jean-philippe@linaro.com>,
Robin Murphy <robin.murphy@arm.com>,
David Woodhouse <dwmw2@infradead.org>,
"Raj, Ashok" <ashok.raj@intel.com>,
"Liu, Yi L" <yi.l.liu@intel.com>
Subject: Re: [PATCH 2/2] iommu/ioasid: Remove custom IOASID allocator
Date: Tue, 14 Feb 2023 10:56:02 -0400 [thread overview]
Message-ID: <Y+uhAvXFq3YKcsuw@nvidia.com> (raw)
In-Reply-To: <BN9PR11MB5276D28B4A4BF8DD3AF1A2828CA29@BN9PR11MB5276.namprd11.prod.outlook.com>
On Tue, Feb 14, 2023 at 06:26:25AM +0000, Tian, Kevin wrote:
> > From: Jason Gunthorpe <jgg@nvidia.com>
> > Sent: Tuesday, February 14, 2023 7:46 AM
> >
> > > > So if a cgroup comes it is just a matter of putting charges in the
> > > > right place which is auditable by looking at calls to attach pasid
> > > > functions.
> > > shouldn't we charge cg during allocation? Or it might be too early for
> > > iommufd so we have to wait until attach?
> >
> > We need to sort this all out. I would expect that iommufd will have an
> > allocation API.
> >
>
> yes.
>
> btw presumably iommu_global_pasid_ida should be move to iommu.c
> since it will be used beyond sva.
Yeah, maybe, I'd think about moving it when we get patches to use it
more than SVA.
Jason
next prev parent reply other threads:[~2023-02-14 14:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 23:02 [PATCH 0/2] Remove VT-d virtual command interface Jacob Pan
2023-02-10 23:02 ` [PATCH 1/2] iommu/vt-d: Remove " Jacob Pan
2023-02-13 2:54 ` Tian, Kevin
2023-02-13 23:19 ` Jason Gunthorpe
2023-02-10 23:02 ` [PATCH 2/2] iommu/ioasid: Remove custom IOASID allocator Jacob Pan
2023-02-13 3:14 ` Tian, Kevin
2023-02-13 16:20 ` Jean-Philippe Brucker
2023-02-13 16:24 ` Jason Gunthorpe
2023-02-13 19:11 ` Jacob Pan
2023-02-13 19:42 ` Jason Gunthorpe
2023-02-13 18:34 ` Jacob Pan
2023-02-13 19:30 ` Jean-Philippe Brucker
2023-02-13 19:48 ` Jason Gunthorpe
2023-02-13 19:39 ` Jason Gunthorpe
2023-02-13 21:44 ` Jacob Pan
2023-02-13 23:18 ` Jason Gunthorpe
2023-02-13 23:43 ` Jacob Pan
2023-02-13 23:45 ` Jason Gunthorpe
2023-02-14 6:26 ` Tian, Kevin
2023-02-14 14:56 ` Jason Gunthorpe [this message]
2023-02-15 1:39 ` Tian, Kevin
2023-02-13 2:52 ` [PATCH 0/2] Remove VT-d virtual command interface Tian, Kevin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y+uhAvXFq3YKcsuw@nvidia.com \
--to=jgg@nvidia.com \
--cc=ashok.raj@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux.dev \
--cc=jacob.jun.pan@linux.intel.com \
--cc=jean-philippe@linaro.com \
--cc=jean-philippe@linaro.org \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=yi.l.liu@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.