From: Jason Gunthorpe <jgg@nvidia.com>
To: Jacob Pan <jacob.pan@linux.microsoft.com>
Cc: kernel test robot <lkp@intel.com>,
linux-kernel@vger.kernel.org,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
Alex Williamson <alex@shazbot.org>,
Joerg Roedel <joro@8bytes.org>,
David Matlack <dmatlack@google.com>,
Nicolin Chen <nicolinc@nvidia.com>,
"Tian, Kevin" <kevin.tian@intel.com>, Yi Liu <yi.l.liu@intel.com>,
Baolu Lu <baolu.lu@linux.intel.com>,
oe-kbuild-all@lists.linux.dev, skhawaja@google.com,
pasha.tatashin@soleen.com,
Jean Philippe-Brucker <jean-philippe@linaro.org>,
Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH 08/11] vfio: Enable cdev noiommu mode under iommufd
Date: Thu, 5 Mar 2026 19:38:27 -0400 [thread overview]
Message-ID: <20260305233827.GA1651202@nvidia.com> (raw)
In-Reply-To: <20260305152614.00001a0f@linux.microsoft.com>
On Thu, Mar 05, 2026 at 03:26:14PM -0800, Jacob Pan wrote:
> Hi Jason,
>
> On Fri, 27 Feb 2026 20:35:40 -0400
> Jason Gunthorpe <jgg@nvidia.com> wrote:
>
> > On Sat, Feb 28, 2026 at 08:18:41AM +0800, kernel test robot wrote:
> > > Kconfig warnings: (for reference only)
> > > WARNING: unmet direct dependencies detected for IOMMU_PT_AMDV1
> > > Depends on [n]: GENERIC_PT [=y] && IOMMU_PT [=y] &&
> > > !GENERIC_ATOMIC64 [=y] Selected by [y]:
> > > - VFIO_NOIOMMU [=y] && VFIO [=y] && VFIO_GROUP [=y]
> >
> > Some kconfig stuff is missing, the iommufd IOMMU would only work with
> > GENERIC_ATOMIC64
> I don't quite understand this dependency on GENERIC_ATOMIC64, or you
> mean the opposite? since we currently have:
Oh, right the inverse.
> config IOMMU_PT_AMDV1
> tristate "IOMMU page table for 64-bit AMD IOMMU v1"
> depends on !GENERIC_ATOMIC64 # for cmpxchg64
>
> And I already have noiommu depends on AMDV1 for mock page tables.
I think it is kconfig not being really transitive with select
dependencies. So things like !GENERIC_ATOMIC64 have to be in the
parent that uses select too.
You could also possibly use depends to avoid this, IIRC.
> Anyway, this particular build issue can be fixed by adding
> IOMMU_SUPPORT. i.e.
That feels indirect, but maybe it is needed too..
Jason
next prev parent reply other threads:[~2026-03-05 23:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 17:52 [PATCH 00/11] iommufd: Enable noiommu mode for cdev Jacob Pan
2026-02-27 17:52 ` [PATCH 01/11] iommufd: Support a HWPT without an iommu driver for noiommu Jacob Pan
2026-02-27 17:52 ` [PATCH 02/11] iommufd: Move igroup allocation to a function Jacob Pan
2026-02-27 17:52 ` [PATCH 03/11] iommufd: Allow binding to a noiommu device Jacob Pan
2026-02-27 17:52 ` [PATCH 04/11] iommufd: Add an ioctl IOMMU_IOAS_GET_PA to query PA from IOVA Jacob Pan
2026-02-27 17:52 ` [PATCH 05/11] vfio: Allow null group for noiommu without containers Jacob Pan
2026-02-27 17:52 ` [PATCH 06/11] vfio: Introduce and set noiommu flag on vfio_device Jacob Pan
2026-02-27 17:52 ` [PATCH 07/11] vfio: Update noiommu device detection logic for cdev Jacob Pan
2026-02-27 17:52 ` [PATCH 08/11] vfio: Enable cdev noiommu mode under iommufd Jacob Pan
2026-02-27 22:03 ` kernel test robot
2026-02-28 0:18 ` kernel test robot
2026-02-28 0:35 ` Jason Gunthorpe
2026-03-05 23:26 ` Jacob Pan
2026-03-05 23:38 ` Jason Gunthorpe [this message]
2026-03-12 16:33 ` Jacob Pan
2026-02-28 0:29 ` kernel test robot
2026-02-27 17:52 ` [PATCH 09/11] vfio:selftest: Handle VFIO noiommu cdev Jacob Pan
2026-02-27 17:52 ` [PATCH 10/11] selftests/vfio: Add iommufd noiommu mode selftest for cdev Jacob Pan
2026-02-27 17:52 ` [PATCH 11/11] Doc: Update VFIO NOIOMMU mode Jacob Pan
2026-03-03 0:35 ` [PATCH 00/11] iommufd: Enable noiommu mode for cdev Jason Gunthorpe
2026-03-03 19:13 ` 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=20260305233827.GA1651202@nvidia.com \
--to=jgg@nvidia.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=jean-philippe@linaro.org \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=nicolinc@nvidia.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pasha.tatashin@soleen.com \
--cc=robin.murphy@arm.com \
--cc=skhawaja@google.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox