mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Logan Gunthorpe <logang@deltatee.com>
To: "Popov, Pavel E" <pavel.e.popov@intel.com>,
	Bjorn Helgaas <helgaas@kernel.org>
Cc: Leon Romanovsky <leon@kernel.org>,
	Jim Chow <jim.chow@broadcom.com>,
	Bjorn Helgaas <bhelgaas@google.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>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	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 0/2] PCI/P2PDMA: Allow P2PDMA in VMware and Hyper-V guests on Intel hosts
Date: Fri, 16 Oct 2026 14:12:08 -0600	[thread overview]
Message-ID: <4af82730-44ff-4ca7-a126-fba78cbf34f4@deltatee.com> (raw)
In-Reply-To: <LV2PR11MB6070A3BB8BCB592EDFAFC261B29B2@LV2PR11MB6070.namprd11.prod.outlook.com>



On 2026-10-16 13:45, Popov, Pavel E wrote:
> 	X86_MATCH_VFM(INTEL_SKYLAKE_X, NULL),
> 	X86_MATCH_VFM(INTEL_ICELAKE_X, NULL),
> 	X86_MATCH_VFM(INTEL_ICELAKE_D, NULL),
> 	X86_MATCH_VFM(INTEL_SAPPHIRERAPIDS_X, NULL),
> 	X86_MATCH_VFM(INTEL_EMERALDRAPIDS_X, NULL),
> 	X86_MATCH_VFM(INTEL_GRANITERAPIDS_X, NULL),
> 	X86_MATCH_VFM(INTEL_GRANITERAPIDS_D, NULL),
> 	X86_MATCH_VFM(INTEL_ATOM_CRESTMONT_X, NULL),	/* Sierra Forest */
> 	X86_MATCH_VFM(INTEL_ATOM_DARKMONT_X, NULL),	/* Clearwater Forest */
> 	X86_MATCH_VFM(INTEL_DIAMONDRAPIDS_X, NULL),

I think this list would be pretty easy to approve if we know the two
Atom parts work.

> If you still prefer the kernel command line option you suggested, v3
> can add it, per-endpoint or global. It works without a patched kernel,
> but puts the burden on every VMware user to know about and set it,
> where v1 or v2 just works.

A kernel command line option probably wouldn't be a bad idea independent
of this. But up to you if you want to try to implement it.

Logan



  reply	other threads:[~2026-10-16 20:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09 15:40 Pavel Popov
2026-10-09 15:40 ` [PATCH 1/2] PCI/P2PDMA: Allow P2PDMA in VMware " Pavel Popov
2026-10-09 16:38   ` Logan Gunthorpe
2026-10-09 16:49     ` Popov, Pavel E
2026-10-09 15:40 ` [PATCH 2/2] PCI/P2PDMA: Allow P2PDMA in Hyper-V " Pavel Popov
2026-10-09 16:58 ` [PATCH 0/2] PCI/P2PDMA: Allow P2PDMA in VMware and " Bjorn Helgaas
2026-10-09 18:08   ` Leon Romanovsky
2026-10-09 18:21     ` Popov, Pavel E
2026-10-09 18:49       ` Leon Romanovsky
2026-10-09 19:13         ` Popov, Pavel E
2026-10-11  5:47           ` Leon Romanovsky
2026-10-12 14:26             ` Popov, Pavel E
2026-10-12 16:24               ` Leon Romanovsky
2026-10-12 16:45                 ` Popov, Pavel E
2026-10-12 18:21                   ` Leon Romanovsky
2026-10-12 20:01                     ` Popov, Pavel E
2026-10-13 12:20                       ` Leon Romanovsky
2026-10-16 14:55                         ` Popov, Pavel E
2026-10-16 15:31                           ` Leon Romanovsky
2026-10-16 16:05                             ` Popov, Pavel E
2026-10-16 18:18                               ` Logan Gunthorpe
2026-10-16 19:45                                 ` Popov, Pavel E
2026-10-16 20:12                                   ` Logan Gunthorpe [this message]
2026-10-16 22:01                                     ` Popov, Pavel E
2026-10-09 19:12     ` Bjorn Helgaas

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=4af82730-44ff-4ca7-a126-fba78cbf34f4@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=rafael@kernel.org \
    --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®