From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Jean-Philippe Brucker <jean-philippe@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
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>,
"Tian, Kevin" <kevin.tian@intel.com>, Yi Liu <yi.l.liu@intel.com>,
jacob.jun.pan@linux.intel.com
Subject: Re: [PATCH 2/2] iommu/ioasid: Remove custom IOASID allocator
Date: Mon, 13 Feb 2023 11:11:52 -0800 [thread overview]
Message-ID: <20230213111152.5ecf734b@jacob-builder> (raw)
In-Reply-To: <Y+pkL5b6mGv40nZy@nvidia.com>
Hi Jason,
On Mon, 13 Feb 2023 12:24:15 -0400, Jason Gunthorpe <jgg@nvidia.com> wrote:
> > We could also merge ioasid.c into iommu-sva.c at this point, since I
> > haven't seen any interest for having multiple IOASID sets on Arm, but
> > I'm not sure what the current plan is for vSVA on x86.
>
> Once the customer allocator is removed this is bascially a thin
> wrapper around xarray
>
> So anything that needs multiple pasid spaces should just create it on
> its own directly with xarray
>
Just wanted to double check that for devices on VT-d platforms that support
both SVA and DMA API with PASID, we will still need a single global pasid
space (due to IOTLB tagging). So this is not the "multiple pasid spaces"
case here, right?
As I replied to Jean as well, we could use the ioasid_set to separate SVA
and DMA API PASIDs.
Thanks,
Jacob
next prev parent reply other threads:[~2023-02-13 19:08 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 [this message]
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
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=20230213111152.5ecf734b@jacob-builder \
--to=jacob.jun.pan@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux.dev \
--cc=jean-philippe@linaro.com \
--cc=jean-philippe@linaro.org \
--cc=jgg@nvidia.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox