From: Logan Gunthorpe <logang@deltatee.com>
To: "Popov, Pavel E" <pavel.e.popov@intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Leon Romanovsky <leon@kernel.org>
Cc: 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>,
Lukas Wunner <lukas@wunner.de>,
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 v2 1/2] PCI/P2PDMA: Allow P2PDMA in VMware guests on Intel hosts
Date: Mon, 19 Oct 2026 15:14:38 -0600 [thread overview]
Message-ID: <fca6d815-519a-449d-a5b7-36bd3ad0c19f@deltatee.com> (raw)
In-Reply-To: <LV2PR11MB607077BABF5643BD4FAF470FB2982@LV2PR11MB6070.namprd11.prod.outlook.com>
On 2026-10-19 13:48, Popov, Pavel E wrote:
> Logan, Leon,
>
> I kept the hypervisor check to avoid changing what the host bridge
> whitelist refuses on bare metal. Looking at those cases again, on the
> listed Xeon CPUs this is a limitation of the whitelist itself, not a
> known hardware limit, and it is why Intel QAT/DSA/IAA had to be added
> by ID. So I'd drop the hypervisor check.
>
> Would a v3 that moves the Xeon list into cpu_supports_p2pdma(), the
> same way as the AMD check, be acceptable to you both?
Yes, that's essentially what I was suggesting before. That would be
acceptable to me.
Thanks,
Logan
next prev parent reply other threads:[~2026-10-19 21:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 22:34 [PATCH v2 0/2] PCI/P2PDMA: Allow P2PDMA in VMware and Hyper-V guests on Intel hosts Pavel Popov
2026-10-16 22:34 ` [PATCH v2 1/2] PCI/P2PDMA: Allow P2PDMA in VMware " Pavel Popov
2026-10-16 22:35 ` sashiko-bot
2026-10-16 22:55 ` Logan Gunthorpe
2026-10-17 0:31 ` Popov, Pavel E
2026-10-17 7:48 ` Leon Romanovsky
2026-10-17 15:21 ` Popov, Pavel E
2026-10-19 19:48 ` Popov, Pavel E
2026-10-19 21:14 ` Logan Gunthorpe [this message]
2026-10-20 5:22 ` Leon Romanovsky
2026-10-16 22:34 ` [PATCH v2 2/2] PCI/P2PDMA: Allow P2PDMA in Hyper-V " Pavel Popov
2026-10-16 22:38 ` sashiko-bot
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=fca6d815-519a-449d-a5b7-36bd3ad0c19f@deltatee.com \
--to=logang@deltatee.com \
--cc=alexey.makhalov@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=jim.chow@broadcom.com \
--cc=leon@kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.