All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: Kevin Tian <kevin.tian@intel.com>, Joerg Roedel <joro@8bytes.org>,
	Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.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>,
	Joel Granados <j.granados@samsung.com>,
	iommu@lists.linux.dev, virtualization@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 00/10] IOMMUFD: Deliver IO page faults to user space
Date: Wed, 12 Jun 2024 10:54:26 -0300	[thread overview]
Message-ID: <20240612135426.GA2151677@nvidia.com> (raw)
In-Reply-To: <20240527040517.38561-1-baolu.lu@linux.intel.com>

On Mon, May 27, 2024 at 12:05:07PM +0800, Lu Baolu wrote:
> This series implements the functionality of delivering IO page faults to
> user space through the IOMMUFD framework. One feasible use case is the
> nested translation. Nested translation is a hardware feature that
> supports two-stage translation tables for IOMMU. The second-stage
> translation table is managed by the host VMM, while the first-stage
> translation table is owned by user space. This allows user space to
> control the IOMMU mappings for its devices.

This looks pretty close, will you post a v7 with the minor changes?

Thanks,
Jasno

  parent reply	other threads:[~2024-06-12 13:54 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-27  4:05 [PATCH v6 00/10] IOMMUFD: Deliver IO page faults to user space Lu Baolu
2024-05-27  4:05 ` [PATCH v6 01/10] iommu: Introduce domain attachment handle Lu Baolu
2024-06-05  8:02   ` Tian, Kevin
2024-06-06  5:33     ` Baolu Lu
2024-06-12 13:10       ` Jason Gunthorpe
2024-06-13  3:04         ` Baolu Lu
2024-05-27  4:05 ` [PATCH v6 02/10] iommu: Remove sva handle list Lu Baolu
2024-06-05  8:15   ` Tian, Kevin
2024-06-06  6:06     ` Baolu Lu
2024-06-07  9:35       ` Tian, Kevin
2024-06-12 13:05         ` Jason Gunthorpe
2024-06-13  4:06           ` Baolu Lu
2024-05-27  4:05 ` [PATCH v6 03/10] iommu: Add attach handle to struct iopf_group Lu Baolu
2024-06-05  8:23   ` Tian, Kevin
2024-06-06  6:18     ` Baolu Lu
2024-06-12 13:37   ` Jason Gunthorpe
2024-06-13  4:23     ` Baolu Lu
2024-06-13 11:49       ` Jason Gunthorpe
2024-06-14  1:16         ` Baolu Lu
2024-05-27  4:05 ` [PATCH v6 04/10] iommu: Extend domain attach group with handle support Lu Baolu
2024-06-12 13:41   ` Jason Gunthorpe
2024-06-13  4:47     ` Baolu Lu
2024-05-27  4:05 ` [PATCH v6 05/10] iommufd: Add fault and response message definitions Lu Baolu
2024-06-05  8:28   ` Tian, Kevin
2024-06-06  6:27     ` Baolu Lu
2024-06-07  9:38       ` Tian, Kevin
2024-06-12 13:19         ` Jason Gunthorpe
2024-06-12 13:50           ` Jason Gunthorpe
2024-06-13  6:32             ` Baolu Lu
2024-06-13  4:54           ` Baolu Lu
2024-06-12 13:52   ` Jason Gunthorpe
2024-06-13  6:40     ` Baolu Lu
2024-05-27  4:05 ` [PATCH v6 06/10] iommufd: Add iommufd fault object Lu Baolu
2024-06-07  9:17   ` Tian, Kevin
2024-06-08  9:58     ` Baolu Lu
2024-06-12 13:25       ` Jason Gunthorpe
2024-06-13  6:44         ` Baolu Lu
2024-06-12 13:23     ` Jason Gunthorpe
2024-06-17  7:32       ` Tian, Kevin
2024-05-27  4:05 ` [PATCH v6 07/10] iommufd: Fault-capable hwpt attach/detach/replace Lu Baolu
2024-06-07  9:30   ` Tian, Kevin
2024-06-09  7:23     ` Baolu Lu
2024-06-17  7:37       ` Tian, Kevin
2024-05-27  4:05 ` [PATCH v6 08/10] iommufd: Associate fault object with iommufd_hw_pgtable Lu Baolu
2024-06-07  9:30   ` Tian, Kevin
2024-05-27  4:05 ` [PATCH v6 09/10] iommufd/selftest: Add IOPF support for mock device Lu Baolu
2024-05-27  4:05 ` [PATCH v6 10/10] iommufd/selftest: Add coverage for IOPF test Lu Baolu
2024-06-12 13:54 ` Jason Gunthorpe [this message]
2024-06-13  6:46   ` [PATCH v6 00/10] IOMMUFD: Deliver IO page faults to user space Baolu Lu

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=20240612135426.GA2151677@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=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=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolinc@nvidia.com \
    --cc=robin.murphy@arm.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=will@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.