From: Leon Romanovsky <leon@kernel.org>
To: "Popov, Pavel E" <pavel.e.popov@intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Logan Gunthorpe <logang@deltatee.com>,
Lukas Wunner <lukas@wunner.de>, Jim Chow <jim.chow@broadcom.com>,
Radu Rugina <radu.rugina@broadcom.com>,
Alexey Makhalov <alexey.makhalov@broadcom.com>,
Wei Liu <wei.liu@kernel.org>,
Michael Kelley <mhklinux@outlook.com>,
Nathan Ciobanu <nathan.d.ciobanu@linux.intel.com>,
"bcm-kernel-feedback-list@broadcom.com"
<bcm-kernel-feedback-list@broadcom.com>,
"virtualization@lists.linux.dev" <virtualization@lists.linux.dev>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 0/2] PCI/P2PDMA: Allow P2PDMA on Intel Xeon server CPUs
Date: Wed, 11 Nov 2026 10:10:57 +0200 [thread overview]
Message-ID: <20261111081057.GP8635@unreal> (raw)
In-Reply-To: <LV2PR11MB6070064A9E674EBDFB1A3B20B2712@LV2PR11MB6070.namprd11.prod.outlook.com>
On Wed, Nov 11, 2026 at 03:48:07AM +0000, Popov, Pavel E wrote:
> Hi Bjorn,
>
> Gentle ping on this series. Is this OK for v7.5?
I would say no. An Intel employee was asked to clean up an Intel-created
mess while upstreaming an Intel-specific patch.
Peer-to-peer is a general concept, and the code should reflect that. It is
reasonable to expect you to join the effort and help clean it up.
Thanks
>
> Thanks,
> Pavel
>
> > -----Original Message-----
> > From: Popov, Pavel E <pavel.e.popov@intel.com>
> > Sent: Tuesday, October 20, 2026 10:38 AM
> > To: Bjorn Helgaas <bhelgaas@google.com>; Logan Gunthorpe
> > <logang@deltatee.com>
> > Cc: Popov, Pavel E <pavel.e.popov@intel.com>; Leon Romanovsky
> > <leon@kernel.org>; Lukas Wunner <lukas@wunner.de>; Jim Chow
> > <jim.chow@broadcom.com>; Radu Rugina <radu.rugina@broadcom.com>;
> > Alexey Makhalov <alexey.makhalov@broadcom.com>; Wei Liu
> > <wei.liu@kernel.org>; Michael Kelley <mhklinux@outlook.com>; Nathan
> > Ciobanu <nathan.d.ciobanu@linux.intel.com>; bcm-kernel-feedback-
> > list@broadcom.com; virtualization@lists.linux.dev; linux-
> > hyperv@vger.kernel.org; linux-pci@vger.kernel.org; linux-
> > kernel@vger.kernel.org
> > Subject: [PATCH v4 0/2] PCI/P2PDMA: Allow P2PDMA on Intel Xeon server
> > CPUs
> >
> > VMware and Hyper-V expose passthrough devices to guest VMs without an
> > explicit host bridge device. Consequently, host_bridge_whitelist() cannot
> > automatically identify the underlying host bridge structure, causing Peer-to-
> > Peer DMA (P2PDMA) requests to be rejected unless the device IDs are
> > explicitly listed in pci_p2pdma_whitelist[]. To enable P2PDMA on Intel hosts,
> > this series extends cpu_supports_p2pdma(), which so far covers AMD Zen and
> > newer, with an explicit list of Intel Xeon server generations.
> >
> > Patch 1 moves the CONFIG_X86 #ifdef out of cpu_supports_p2pdma().
> > Patch 2 is the v3 patch rebased on it, with Logan's Reviewed-by carried over;
> > the Xeon list and the check are unchanged.
> >
> > Changes in v4:
> > - Add 1/2, moving the CONFIG_X86 #ifdef out of cpu_supports_p2pdma()
> > (Logan Gunthorpe, Leon Romanovsky)
> > - Keep the #ifdef around the asm/ includes, as these headers exist
> > only on x86 (Bjorn Helgaas)
> >
> > Changes in v3:
> > - Drop the hypervisor check and move the Xeon list into
> > cpu_supports_p2pdma(), next to the AMD check, as suggested by Logan
> > Gunthorpe and Leon Romanovsky [1]
> > - Fold the VMware and Hyper-V patches into one, as the check no longer
> > depends on the hypervisor
> >
> > Changes in v2:
> > - Replace the Skylake-and-newer threshold with an explicit list of Intel
> > Xeon server generations, from Skylake-SP to Diamond Rapids (Logan
> > Gunthorpe)
> > - Move the CONFIG_X86 #ifdef out of hypervisor_supports_p2pdma()
> > (Logan Gunthorpe)
> > - Rebased on current mainline
> >
> > [1] https://lore.kernel.org/r/20261016153147.GC219304@unreal
> >
> > v3: https://lore.kernel.org/r/20261020151305.65218-1-
> > pavel.e.popov@intel.com
> > v2: https://lore.kernel.org/r/20261016223402.19991-1-
> > pavel.e.popov@intel.com
> > v1: https://lore.kernel.org/r/20261009154034.82321-1-
> > pavel.e.popov@intel.com
> >
> > Pavel Popov (2):
> > PCI/P2PDMA: Move CONFIG_X86 #ifdef out of cpu_supports_p2pdma()
> > PCI/P2PDMA: Allow P2PDMA on Intel Xeon server CPUs
> >
> > drivers/pci/p2pdma.c | 33 +++++++++++++++++++++++++++++++--
> > 1 file changed, 31 insertions(+), 2 deletions(-)
> >
> >
> > base-commit: c03c1a14507dfaf8b856c2608f9ac216021fc222
> > --
> > 2.53.0
>
prev parent reply other threads:[~2026-11-11 8:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 17:37 Pavel Popov
2026-10-20 17:37 ` [PATCH v4 1/2] PCI/P2PDMA: Move CONFIG_X86 #ifdef out of cpu_supports_p2pdma() Pavel Popov
2026-10-20 17:37 ` [PATCH v4 2/2] PCI/P2PDMA: Allow P2PDMA on Intel Xeon server CPUs Pavel Popov
2026-10-20 18:40 ` [PATCH v4 0/2] " Leon Romanovsky
2026-10-20 19:37 ` Popov, Pavel E
2026-10-21 7:34 ` Leon Romanovsky
2026-10-21 13:07 ` Popov, Pavel E
2026-11-11 3:48 ` Popov, Pavel E
2026-11-11 8:10 ` Leon Romanovsky [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=20261111081057.GP8635@unreal \
--to=leon@kernel.org \
--cc=alexey.makhalov@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=jim.chow@broadcom.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=lukas@wunner.de \
--cc=mhklinux@outlook.com \
--cc=nathan.d.ciobanu@linux.intel.com \
--cc=pavel.e.popov@intel.com \
--cc=radu.rugina@broadcom.com \
--cc=virtualization@lists.linux.dev \
--cc=wei.liu@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
all inboxes | Powered by JetHome®