[<prev] [next>] [day] [month] [year] [list]
Message-ID: <c918825d-ad74-4b1d-abcc-31c3f3ea4620@linux.intel.com>
Date: Fri, 9 Feb 2024 10:39:44 +0800
From: Baolu Lu <baolu.lu@...ux.intel.com>
To: Zhangfei Gao <zhangfei.gao@...aro.org>
Cc: baolu.lu@...ux.intel.com, Joerg Roedel <joro@...tes.org>,
Will Deacon <will@...nel.org>, Robin Murphy <robin.murphy@....com>,
Jason Gunthorpe <jgg@...pe.ca>, Kevin Tian <kevin.tian@...el.com>,
Jean-Philippe Brucker <jean-philippe@...aro.org>,
Nicolin Chen <nicolinc@...dia.com>, Yi Liu <yi.l.liu@...el.com>,
Jacob Pan <jacob.jun.pan@...ux.intel.com>,
Longfang Liu <liulongfang@...wei.com>, Yan Zhao <yan.y.zhao@...el.com>,
Joel Granados <j.granados@...sung.com>, iommu@...ts.linux.dev,
kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v12 00/16] iommu: Prepare to deliver page faults to user
space
On 2024/2/8 17:03, Zhangfei Gao wrote:
> Hi, Baolu
>
> On Wed, 7 Feb 2024 at 09:39, Lu Baolu <baolu.lu@...ux.intel.com
> <mailto:baolu.lu@...ux.intel.com>> wrote:
>
> When a user-managed page table is attached to an IOMMU, it is necessary
> to deliver IO page faults to user space so that they can be handled
> appropriately. One use case for this is nested translation, which is
> currently being discussed in the mailing list.
>
> I have posted a RFC series [1] that describes the implementation of
> delivering page faults to user space through IOMMUFD. This series has
> received several comments on the IOMMU refactoring, which I am trying to
> address in this series.
>
> The major refactoring includes:
>
> - [PATCH 01 ~ 04] Move include/uapi/linux/iommu.h to
> include/linux/iommu.h. Remove the unrecoverable fault data
> definition.
> - [PATCH 05 ~ 06] Remove iommu_[un]register_device_fault_handler().
> - [PATCH 07 ~ 10] Separate SVA and IOPF. Make IOPF a generic page fault
> handling framework.
> - [PATCH 11 ~ 16] Improve iopf framework.
>
> This is also available at github [2].
>
> [1]
> https://lore.kernel.org/linux-iommu/20230530053724.232765-1-baolu.lu@linux.intel.com/ <https://lore.kernel.org/linux-iommu/20230530053724.232765-1-baolu.lu@linux.intel.com/>
> [2]
> https://github.com/LuBaolu/intel-iommu/commits/preparatory-io-pgfault-delivery-v12 <https://github.com/LuBaolu/intel-iommu/commits/preparatory-io-pgfault-delivery-v12>
>
>
> Wandering are these patches dropped now,
>
> [PATCH v2 2/6] iommufd: Add iommu page fault uapi data
> https://lore.kernel.org/lkml/20231026024930.382898-3-baolu.lu@linux.intel.com/raw <https://lore.kernel.org/lkml/20231026024930.382898-3-baolu.lu@linux.intel.com/raw>
>
> [PATCH v2 4/6] iommufd: Deliver fault messages to user space
> https://lore.kernel.org/lkml/20231026024930.382898-5-baolu.lu@linux.intel.com/ <https://lore.kernel.org/lkml/20231026024930.382898-5-baolu.lu@linux.intel.com/>
Above patches are part of another series named "IOMMUFD: Deliver IO page
faults to user space", which is now updated to v3.
https://lore.kernel.org/linux-iommu/20240122073903.24406-1-baolu.lu@linux.intel.com/
> And does iouring still be used in user space?
iouring is not related to this series. For uapi of iommufd, it's still
recommended to use iouring to speed up the handling of faults.
Best regards,
baolu
Powered by blists - more mailing lists