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 08:41:58 -0300 [thread overview]
Message-ID: <20260817114158.GA1175472@nvidia.com> (raw)
In-Reply-To: <PA1P190MB2557D53CB7FCB70EB8F79D09DBA72@PA1P190MB2557.EURP190.PROD.OUTLOOK.COM>
On Mon, Aug 17, 2026 at 09:29:10AM +0000, Dmitry Malkin wrote:
> > Don't use it that way?
>
> Why not? We use pci=config_acs to configure ACS at kernel startup
> and enable direct PCIe peer-to-peer traffic between GPUs and
> NICs. All affected devices are assigned to the same VM and IOMMU
> domain, which also reduces the memory footprint by reducing the
> number of page tables and lowers IOTLB pressure.
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.
Then you don't have issues here.
Jason
next prev parent reply other threads:[~2026-08-17 11:42 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 [this message]
2026-08-17 14:26 ` Dmitry Malkin
2026-08-17 15:20 ` Jason Gunthorpe
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=20260817114158.GA1175472@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