[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220524211024.GC1343366@nvidia.com>
Date: Tue, 24 May 2022 18:10:24 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: Jacob Pan <jacob.jun.pan@...ux.intel.com>
Cc: iommu@...ts.linux-foundation.org,
LKML <linux-kernel@...r.kernel.org>, dmaengine@...r.kernel.org,
Joerg Roedel <joro@...tes.org>,
David Woodhouse <dwmw2@...radead.org>,
Jean-Philippe Brucker <jean-philippe@...aro.com>,
Lu Baolu <baolu.lu@...ux.intel.com>,
Christoph Hellwig <hch@...radead.org>, vkoul@...nel.org,
robin.murphy@....com, will@...nel.org, Yi Liu <yi.l.liu@...el.com>,
Dave Jiang <dave.jiang@...el.com>,
"Tian, Kevin" <kevin.tian@...el.com>,
Raj Ashok <ashok.raj@...el.com>,
Eric Auger <eric.auger@...hat.com>
Subject: Re: [PATCH v4 3/6] iommu/vt-d: Implement domain ops for
attach_dev_pasid
On Tue, May 24, 2022 at 01:45:26PM -0700, Jacob Pan wrote:
> > The idea that there is only one PASID per domain per device is not
> > right.
> >
> Got you, I was under the impression that there is no use case yet for
> multiple PASIDs per device-domain based on our early discussion.
The key word there is "in-kernel" and "DMA API" - iommufd userspace
will do whatever it likes.
I wish you guys would organize your work so adding generic PASID
support to IOMMU was its own series with its own purpose so everything
stops becoming confused with SVA and DMA API ideas that are not
general.
Jason
Powered by blists - more mailing lists