From: Baolu Lu <baolu.lu@linux.intel.com>
To: Zhangfei Gao <zhangfei.gao@linaro.org>
Cc: baolu.lu@linux.intel.com, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Kevin Tian <kevin.tian@intel.com>,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
Nicolin Chen <nicolinc@nvidia.com>, Yi Liu <yi.l.liu@intel.com>,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
Longfang Liu <liulongfang@huawei.com>,
Yan Zhao <yan.y.zhao@intel.com>,
Joel Granados <j.granados@samsung.com>,
iommu@lists.linux.dev, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v12 00/16] iommu: Prepare to deliver page faults to user space
Date: Fri, 9 Feb 2024 10:39:44 +0800 [thread overview]
Message-ID: <c918825d-ad74-4b1d-abcc-31c3f3ea4620@linux.intel.com> (raw)
In-Reply-To: <CABQgh9H02z+uHg_hYnoVZURz7PLeYW_41MwxciE6W+kPRgEHsw@mail.gmail.com>
On 2024/2/8 17:03, Zhangfei Gao wrote:
> Hi, Baolu
>
> On Wed, 7 Feb 2024 at 09:39, Lu Baolu <baolu.lu@linux.intel.com
> <mailto:baolu.lu@linux.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
prev parent reply other threads:[~2024-02-09 2:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 1:33 [PATCH v12 00/16] iommu: Prepare to deliver page faults to user space Lu Baolu
2024-02-07 1:33 ` [PATCH v12 01/16] iommu: Move iommu fault data to linux/iommu.h Lu Baolu
2024-02-07 1:33 ` [PATCH v12 02/16] iommu/arm-smmu-v3: Remove unrecoverable faults reporting Lu Baolu
2024-02-07 1:33 ` [PATCH v12 03/16] iommu: Remove unrecoverable fault data Lu Baolu
2024-02-07 1:33 ` [PATCH v12 04/16] iommu: Cleanup iopf data structure definitions Lu Baolu
2024-02-07 1:33 ` [PATCH v12 05/16] iommu: Merge iopf_device_param into iommu_fault_param Lu Baolu
2024-02-07 1:33 ` [PATCH v12 06/16] iommu: Remove iommu_[un]register_device_fault_handler() Lu Baolu
2024-02-07 1:33 ` [PATCH v12 07/16] iommu: Merge iommu_fault_event and iopf_fault Lu Baolu
2024-02-07 1:33 ` [PATCH v12 08/16] iommu: Prepare for separating SVA and IOPF Lu Baolu
2024-02-07 1:33 ` [PATCH v12 09/16] iommu: Make iommu_queue_iopf() more generic Lu Baolu
2024-02-07 1:33 ` [PATCH v12 10/16] iommu: Separate SVA and IOPF Lu Baolu
2024-02-07 1:33 ` [PATCH v12 11/16] iommu: Refine locking for per-device fault data management Lu Baolu
2024-02-07 1:33 ` [PATCH v12 12/16] iommu: Use refcount for fault data access Lu Baolu
2024-02-07 1:33 ` [PATCH v12 13/16] iommu: Improve iopf_queue_remove_device() Lu Baolu
2024-02-07 2:50 ` Tian, Kevin
2024-02-07 12:29 ` Baolu Lu
2024-02-07 17:59 ` Vasant Hegde
2024-02-08 1:32 ` Baolu Lu
2024-02-08 5:06 ` Vasant Hegde
2024-02-07 1:33 ` [PATCH v12 14/16] iommu: Track iopf group instead of last fault Lu Baolu
2024-02-07 1:33 ` [PATCH v12 15/16] iommu: Make iopf_group_response() return void Lu Baolu
2024-02-07 1:33 ` [PATCH v12 16/16] iommu: Make iommu_report_device_fault() " Lu Baolu
2024-02-08 9:11 ` [PATCH v12 00/16] iommu: Prepare to deliver page faults to user space Zhangfei Gao
[not found] ` <CABQgh9H02z+uHg_hYnoVZURz7PLeYW_41MwxciE6W+kPRgEHsw@mail.gmail.com>
2024-02-09 2:39 ` Baolu Lu [this message]
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=c918825d-ad74-4b1d-abcc-31c3f3ea4620@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=j.granados@samsung.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=jean-philippe@linaro.org \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liulongfang@huawei.com \
--cc=nicolinc@nvidia.com \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
--cc=yan.y.zhao@intel.com \
--cc=yi.l.liu@intel.com \
--cc=zhangfei.gao@linaro.org \
/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