[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f7b0cbef-3d7d-e5aa-1971-fe230d0c80e1@linux.intel.com>
Date: Tue, 7 Mar 2023 09:41:42 +0800
From: Baolu Lu <baolu.lu@...ux.intel.com>
To: Fenghua Yu <fenghua.yu@...el.com>, Vinod Koul <vkoul@...nel.org>,
Dave Jiang <dave.jiang@...el.com>
Cc: baolu.lu@...ux.intel.com, dmaengine@...r.kernel.org,
linux-kernel <linux-kernel@...r.kernel.org>,
Alistair Popple <apopple@...dia.com>,
Joerg Roedel <joro@...tes.org>, Will Deacon <will@...nel.org>,
Robin Murphy <robin.murphy@....com>,
Lorenzo Stoakes <lstoakes@...il.com>,
Christoph Hellwig <hch@...radead.org>, iommu@...ts.linux.dev
Subject: Re: [PATCH v2 08/16] iommu: define and export
iommu_access_remote_vm()
On 3/7/23 12:31 AM, Fenghua Yu wrote:
> Define and export iommu_access_remote_vm() to allow IOMMU related
> drivers to access user address space by PASID.
>
> The IDXD driver would like to use it to write the user's completion
> record that the hardware device is not able to write to due to user
> page fault.
I don't quite follow here. Isn't I/O page fault already supported?
Best regards,
baolu
Powered by blists - more mailing lists