From: Bjorn Helgaas <helgaas@kernel.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: bhelgaas@google.com, linux-pci@vger.kernel.org,
jonathan.derrick@linux.dev, lpieralisi@kernel.org,
kwilczynski@kernel.org, mani@kernel.org, robh@kernel.org,
Dexuan Cui <decui@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
"K. Y. Srinivasan" <kys@microsoft.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Michael Kelley <mhklinux@outlook.com>,
Nirmal Patel <nirmal.patel@linux.intel.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Szymon Durawa <szymon.durawa@linux.intel.com>,
Wei Liu <wei.liu@kernel.org>
Subject: Re: [PATCH v2 0/2] PCI: Unify domain emulation
Date: Tue, 28 Oct 2025 12:39:25 -0500 [thread overview]
Message-ID: <20251028173925.GA1521899@bhelgaas> (raw)
In-Reply-To: <20251024224622.1470555-1-dan.j.williams@intel.com>
On Fri, Oct 24, 2025 at 03:46:20PM -0700, Dan Williams wrote:
> Changes since v1 [1]:
> - Rebase on v6.18-rc2
> - Support callers supplying both a hint and a range for the Hyper-V hint
> + fallback case (Michael)
> - Add comment explaining domain number 0 vs Gen1 VMs, and domain values
> greater than U16_MAX concerns (Michael)
> - Leave the VMD status quo comment about requesting domain numbers >
> U16_MAX
>
> [1]: http://lore.kernel.org/20250716160835.680486-1-dan.j.williams@intel.com
>
> The PCI/TSM effort created a sample driver to test ABI flows
> (samples/devsec/ [2]). Suzuki observed that it only worked on x86 due to
> its dependency on CONFIG_PCI_DOMAINS_GENERIC=n. I.e. an unfortunate
> restriction for what should be an architecture agnostic test framework.
>
> Introduce a new pci_bus_find_emul_domain_nr() helper that all "soft"
> host-bridge drivers can share and hide the CONFIG_PCI_DOMAINS_GENERIC
> details behind that helper.
>
> [2]: https://git.kernel.org/pub/scm/linux/kernel/git/devsec/tsm.git/commit/?id=0e16ce0b9c64
>
> Dan Williams (2):
> PCI: Enable host bridge emulation for PCI_DOMAINS_GENERIC platforms
> PCI: vmd: Switch to pci_bus_find_emul_domain_nr()
>
> include/linux/pci.h | 7 ++++
> drivers/pci/controller/pci-hyperv.c | 62 +++++------------------------
> drivers/pci/controller/vmd.c | 40 ++++++++-----------
> drivers/pci/pci.c | 24 ++++++++++-
> drivers/pci/probe.c | 8 +++-
> 5 files changed, 63 insertions(+), 78 deletions(-)
Applied to pci/enumeration for v6.19, thanks, Dan!
prev parent reply other threads:[~2025-10-28 17:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 22:46 [PATCH v2 0/2] PCI: Unify domain emulation Dan Williams
2025-10-24 22:46 ` [PATCH v2 1/2] PCI: Enable host bridge emulation for PCI_DOMAINS_GENERIC platforms Dan Williams
2025-10-25 19:53 ` Michael Kelley
2025-10-27 23:45 ` dan.j.williams
2025-10-27 20:08 ` Dave Jiang
2025-10-24 22:46 ` [PATCH v2 2/2] PCI: vmd: Switch to pci_bus_find_emul_domain_nr() Dan Williams
2025-10-27 20:08 ` Dave Jiang
2025-10-28 17:39 ` Bjorn Helgaas [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=20251028173925.GA1521899@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=jonathan.derrick@linux.dev \
--cc=kwilczynski@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mhklinux@outlook.com \
--cc=nirmal.patel@linux.intel.com \
--cc=robh@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=szymon.durawa@linux.intel.com \
--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