The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Yi Liu <yi.l.liu@intel.com>
To: Jacob Pan <jacob.pan@linux.microsoft.com>
Cc: <linux-kernel@vger.kernel.org>,
	"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
	Jason Gunthorpe <jgg@nvidia.com>,
	Alex Williamson <alex@shazbot.org>,
	Joerg Roedel <joro@8bytes.org>,
	Mostafa Saleh <smostafa@google.com>,
	David Matlack <dmatlack@google.com>,
	Robin Murphy <robin.murphy@arm.com>,
	Nicolin Chen <nicolinc@nvidia.com>,
	"Tian, Kevin" <kevin.tian@intel.com>,
	Baolu Lu <baolu.lu@linux.intel.com>,
	Saurabh Sengar <ssengar@linux.microsoft.com>,
	<skhawaja@google.com>, <pasha.tatashin@soleen.com>,
	Will Deacon <will@kernel.org>
Subject: Re: [PATCH v6 7/7] Documentation: Update VFIO NOIOMMU mode
Date: Mon, 25 May 2026 14:29:23 +0800	[thread overview]
Message-ID: <3ff06437-e125-40dc-affe-b234241129cf@intel.com> (raw)
In-Reply-To: <20260522204210.00002858@linux.microsoft.com>

On 5/23/26 11:42, Jacob Pan wrote:
> Hi Yi,
> 
> On Fri, 22 May 2026 17:42:42 +0800
> Yi Liu <yi.l.liu@intel.com> wrote:
> 
>>> ++------+-------+-----------+------+---------+---------------------------+
>>> +| Case | GROUP | Container | CDEV | NOIOMMU | Notes
>>>       |
>>> ++======+=======+===========+======+=========+===========================+
>>> +|  1   |   y   |     y     |  n   |   yes   | Group noiommu works
>>>       |
>>> ++------+-------+-----------+------+---------+---------------------------+
>>> +|  2   |   y   |     n     |  n   |   no    | Blocked - no
>>> container    |
>>> ++------+-------+-----------+------+---------+---------------------------+
>>> +|  3   |   y   |     y     |  y   |   yes   | Both paths work
>>>       |
>>> ++------+-------+-----------+------+---------+---------------------------+
>>> +|  4   |   y   |     n     |  y   |   no    | Blocked - no
>>> container    |
>>> ++------+-------+-----------+------+---------+---------------------------+
>>> +|  5   |   n   |     -     |  y   |   yes   | Cdev-only works
>>>       |
>>> ++------+-------+-----------+------+---------+---------------------------+
>>> +|  6   |   n   |     -     |  n   |   no    | No access path
>>>       |
>>> ++------+-------+-----------+------+---------+---------------------------+
>>> +
>>
>> Does "Bloked" mean no access path or no chance to compile? :)
> By “Blocked”, I mean Kconfig prevents that combination from being
> selected, so it is not buildable as such; consequently there is no
> access path at runtime.

got it. :)

Reviewed-by: Yi Liu <yi.l.liu@intel.com>

  reply	other threads:[~2026-05-25  6:21 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-21 22:11 [PATCH v6 0/7] iommufd: Enable noiommu mode for cdev Jacob Pan
2026-05-21 22:11 ` [PATCH v6 1/7] iommufd: Support a HWPT without an iommu driver for noiommu Jacob Pan
2026-05-21 22:11 ` [PATCH v6 2/7] iommufd: Move igroup allocation to a function Jacob Pan
2026-05-22  6:00   ` Baolu Lu
2026-05-21 22:11 ` [PATCH v6 3/7] iommufd: Allow binding to a noiommu device Jacob Pan
2026-05-22  6:01   ` Baolu Lu
2026-05-21 22:11 ` [PATCH v6 4/7] iommufd: Add an ioctl to query PA from IOVA for noiommu mode Jacob Pan
2026-05-22  9:22   ` Yi Liu
2026-05-21 22:11 ` [PATCH v6 5/7] vfio: Enable cdev noiommu mode under iommufd Jacob Pan
2026-05-22  9:19   ` Yi Liu
2026-05-23 22:01     ` Jacob Pan
2026-05-25  6:29       ` Yi Liu
2026-05-28 18:52         ` Jacob Pan
2026-05-29  7:27           ` Yi Liu
2026-05-21 22:11 ` [PATCH v6 6/7] selftests/vfio: Add iommufd noiommu mode selftest for cdev Jacob Pan
2026-05-21 22:39   ` David Matlack
2026-06-03  0:13     ` Jacob Pan
2026-05-21 22:11 ` [PATCH v6 7/7] Documentation: Update VFIO NOIOMMU mode Jacob Pan
2026-05-22  9:42   ` Yi Liu
2026-05-23  3:42     ` Jacob Pan
2026-05-25  6:29       ` Yi Liu [this message]
2026-05-25  8:30 ` [PATCH v6 0/7] iommufd: Enable noiommu mode for cdev Tian, Kevin
2026-05-26 15:32   ` Jacob Pan
2026-05-26 17:57     ` Alex Williamson
2026-05-27 22:34       ` Jacob Pan

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=3ff06437-e125-40dc-affe-b234241129cf@intel.com \
    --to=yi.l.liu@intel.com \
    --cc=alex@shazbot.org \
    --cc=baolu.lu@linux.intel.com \
    --cc=dmatlack@google.com \
    --cc=iommu@lists.linux.dev \
    --cc=jacob.pan@linux.microsoft.com \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolinc@nvidia.com \
    --cc=pasha.tatashin@soleen.com \
    --cc=robin.murphy@arm.com \
    --cc=skhawaja@google.com \
    --cc=smostafa@google.com \
    --cc=ssengar@linux.microsoft.com \
    --cc=will@kernel.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