From: Jason Gunthorpe <jgg@nvidia.com>
To: Dmitry Malkin <dma@nebius.com>
Cc: Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <joro@8bytes.org>,
Nicolin Chen <nicolinc@nvidia.com>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
NB-Core Team <NB-CoreTeam@nebius.com>
Subject: Re: [RFC PATCH] iommu/arm-smmu-v3: Allow nested attach for PCI bridges without vDEVICE
Date: Mon, 17 Aug 2026 12:20:51 -0300 [thread overview]
Message-ID: <20260817152051.GB1410416@nvidia.com> (raw)
In-Reply-To: <PA1P190MB255719949EC777E6D2DB2606DBA72@PA1P190MB2557.EURP190.PROD.OUTLOOK.COM>
On Mon, Aug 17, 2026 at 02:26:46PM +0000, Dmitry Malkin wrote:
>
> > This kind of situation is very challenging to setup in the VM, and at
> > this point you may as well include the switch to the VM too.
>
> Passing through the PCI switch would not help because the device without
> a vDEVICE is the host Root Port. Neither the Root Port nor the switch
> should be exposed to the VM.
Oh that's probably because of the unfixed grouping bugs in the
kernel. The root port should not be part of the group with correctly
set ACS flags for switch P2P.
> A multi-device IOMMU group is an intentional effect of using
> 'pci=config_acs', and I would prefer to restore support for this
> configuration upstream.
It doesn't work. We tried to make it work, there are many problems
unfortunately. Don't use multi-device groups in the hypervisor.
This patch is pure hacky, there is no good justification for the
kernel to ignore certain devices in the group inside an iommu driver.
Jason
prev parent reply other threads:[~2026-08-17 15:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 10:07 [RFC PATCH] iommu/arm-smmu-v3: Allow nested attach for PCI bridges without vDEVICE Dmitry Malkin
2026-08-14 14:15 ` Pranjal Shrivastava
2026-08-14 15:40 ` Dmitry Malkin
2026-08-14 17:49 ` Jason Gunthorpe
2026-08-14 17:48 ` Jason Gunthorpe
2026-08-14 18:56 ` Dmitry Malkin
2026-08-14 22:11 ` Jason Gunthorpe
2026-08-17 9:29 ` Dmitry Malkin
2026-08-17 11:16 ` Pranjal Shrivastava
2026-08-17 11:44 ` Jason Gunthorpe
2026-08-17 12:53 ` Pranjal Shrivastava
2026-08-17 11:41 ` Jason Gunthorpe
2026-08-17 14:26 ` Dmitry Malkin
2026-08-17 15:20 ` Jason Gunthorpe [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=20260817152051.GB1410416@nvidia.com \
--to=jgg@nvidia.com \
--cc=NB-CoreTeam@nebius.com \
--cc=dma@nebius.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=regressions@lists.linux.dev \
--cc=robin.murphy@arm.com \
--cc=stable@vger.kernel.org \
--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