Re: [PATCH v6 7/7] Documentation: Update VFIO NOIOMMU mode

[Jacob Pan <jacob.pan@linux.microsoft.com>]

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.