From: Logan Gunthorpe <logang@deltatee.com>
To: "Popov, Pavel E" <pavel.e.popov@intel.com>,
Bjorn Helgaas <helgaas@kernel.org>,
Leon Romanovsky <leon@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.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 v3] PCI/P2PDMA: Allow P2PDMA on Intel Xeon server CPUs
Date: Tue, 20 Oct 2026 10:54:39 -0600 [thread overview]
Message-ID: <db26b21b-8416-4b11-aed8-3829ed5a6cfa@deltatee.com> (raw)
In-Reply-To: <LV2PR11MB6070444E927B9AA891B8180FB2672@LV2PR11MB6070.namprd11.prod.outlook.com>
On 2026-10-20 10:47, Popov, Pavel E wrote:
> If preferred, we could use for cpu_supports_p2pdma() the pattern Logan
> suggested for hypervisor_supports_p2pdma() in v1: the whole function
> under #ifdef CONFIG_X86 with a stub returning false for !CONFIG_X86.
> The Intel CPU list then moves into the same #ifdef block, which saves
> one #ifdef, at the cost of also touching the existing AMD part.
I personally would prefer cleaning up the #ifdef style but that's an
issue that's already in the code. I don't feel the need to make it
conditional on my Reviewed-by. If you are able to clean that up, I would
appreciate it.
Thanks,
Logan
next prev parent reply other threads:[~2026-10-20 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 15:13 Pavel Popov
2026-10-20 16:08 ` Logan Gunthorpe
2026-10-20 16:14 ` Leon Romanovsky
2026-10-20 16:37 ` Bjorn Helgaas
2026-10-20 16:47 ` Popov, Pavel E
2026-10-20 16:54 ` Logan Gunthorpe [this message]
2026-10-20 17:16 ` Leon Romanovsky
2026-10-20 17:19 ` Leon Romanovsky
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=db26b21b-8416-4b11-aed8-3829ed5a6cfa@deltatee.com \
--to=logang@deltatee.com \
--cc=alexey.makhalov@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--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 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®