From: Tushar Dave <tdave@nvidia.com>
To: qemu-devel@nongnu.org
Cc: alwilliamson@nvidia.com, jgg@nvidia.com, skolothumtho@nvidia.com,
qemu-arm@nongnu.org, peter.maydell@linaro.org, mst@redhat.com,
marcel.apfelbaum@gmail.com, devel@edk2.groups.io
Subject: [RFC PATCH 0/8] hw/arm/virt, hw/pci: PCI pre-enumeration and fixed BAR allocation
Date: Fri, 8 May 2026 13:37:09 -0500 [thread overview]
Message-ID: <20260508183717.193630-1-tdave@nvidia.com> (raw)
This RFC introduces a mechanism to specify Guest Physical Addresses
(GPAs) for PCI BARs, allowing explicit placement of guest MMIO BAR
addresses to match host physical addresses for assigned devices.
On some platforms, P2P DMA is performed between devices within the same
IOMMU group. The PCI fabric ACS is configured to permit direct P2P
without going through the host bridge in order to achieve the required
performance.
To support this multi-device IOMMU group P2P scenario in virtualization,
the VM may need to use the same MMIO BAR addresses as the host physical
address layout.
This series implements a per-device PCI property, "fixed-bars", which
allows users to specify fixed BAR addresses. The property is generic
and is available on any PCI-capable machine. It is a comma-separated
list of BAR assignments:
barN@<addr>[,barM@<addr>]*
The virt machine builds on this with two additional machine properties:
pci-pre-enum
When enabled, QEMU performs PCI enumeration and resource assignment
before handing control to firmware (e.g. EDK2). This includes
programming 64-bit prefetchable BARs according to fixed-bars
assignments, and programming bridge prefetchable windows.
A "pci-enum-done" device-tree property is set so firmware preserves
the configuration.
pcie-mmio-window
Defines the MMIO64 window for PCIe devices. When using fixed-bars,
this allows the aperture to be resized or repositioned so all
assigned BARs fall within a valid address range.
Why QEMU programs PCI resources rather than EDK2:
To support fixed BAR placement, QEMU performs PCI bus enumeration and
resource assignment prior to firmware execution. EDK2 already provides
a PCD-controlled mechanism (PcdPciDisableBusEnumeration) that allows
the platform to skip PCI enumeration and resource allocation. This
series leverages that mechanism so that, when enabled, firmware runs in
a discovery-only mode and preserves the configuration established by
QEMU.
When pci-pre-enum is enabled, QEMU runs PCI enumeration and resource
allocation, prioritizing fixed BARs specified via fixed-bars. If
allocation fails due to alignment, overlap, or address space constraints,
QEMU terminates with an error. Otherwise, all BARs and bridge windows are
fully programmed before firmware execution.
There is certainly room for improvement, but this RFC aims to gather
feedback on the overall approach chosen to address this problem.
We use the virt machine in this series as the concrete example
consuming the fixed-BAR model. Other machines may require their own
machine-specific mechanism (such as pcie-mmio-window) if they want to
adopt the same approach.
Example usage:
-machine virt,...,pcie-mmio-window=0x400000000000:0x400000000000,pci-pre-enum=on \
-device vfio-pci,host=0009:06:00.0,id=dev0 \
-set device.dev0.fixed-bars=bar2@0x6b8000000000,bar4@0x6c8000000000
Testing:
This series was tested on NVIDIA GB300 platforms with a recent Linux
kernel. GPUDirect P2P between a GPU and a CX8 NIC requires a PCIe
topology in the VM that mirrors bare metal (e.g. both devices under the
same switch and ACS tuned for the minimal P2P paths needed for GPUDirect
RDMA).
TODO:
- The fixed BAR allocator handles 64-bit prefetchable BARs and related
bridge prefetch windows only. Programming PIO, 32-bit MMIO, and
64-bit non-prefetchable BARs, and sizing bridge windows for those
resource types, is left for follow-up patches.
- SR-IOV virtual functions are not included when sizing bridge prefetch
apertures and may require additional work.
- Add ACPI _DSM so the fixed BARs are preserved.
A git branch with this series applied is available at:
https://github.com/tdavenvidia/upstream-qemu/commits/upstream_May_08_26/
The related EDK2 change is available at:
https://github.com/tdavenvidia/edk2/commits/upstream_May_08_26/
Tushar Dave (8):
hw/pci: add fixed-bars property to allow fixed BAR addresses
hw/pci: enumerate PCI bus and program bridge bus numbers
hw/pci: introduce allocator for fixed BAR placement
hw/pci: pack remaining BARs and update bridge windows
hw/pci: allocate remaining BARs for buses without fixed BARs
hw/pci: finalize bridge prefetch windows after BAR allocation
hw/arm/virt: add pcie-mmio-window machine property
hw/arm/virt: add pci-pre-enum machine property
hw/arm/virt.c | 157 ++++-
hw/pci/meson.build | 2 +
hw/pci/pci-enumerate.c | 144 +++++
hw/pci/pci-enumerate.h | 15 +
hw/pci/pci-resource.c | 1099 +++++++++++++++++++++++++++++++++++
hw/pci/pci-resource.h | 82 +++
hw/pci/pci.c | 108 ++++
include/hw/arm/virt.h | 3 +
include/hw/pci/pci_device.h | 10 +
9 files changed, 1615 insertions(+), 5 deletions(-)
create mode 100644 hw/pci/pci-enumerate.c
create mode 100644 hw/pci/pci-enumerate.h
create mode 100644 hw/pci/pci-resource.c
create mode 100644 hw/pci/pci-resource.h
--
2.34.1
next reply other threads:[~2026-05-08 20:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 18:37 Tushar Dave [this message]
2026-05-08 18:37 ` [RFC PATCH 1/8] hw/pci: add fixed-bars property to allow fixed BAR addresses Tushar Dave
2026-05-08 18:37 ` [RFC PATCH 2/8] hw/pci: enumerate PCI bus and program bridge bus numbers Tushar Dave
2026-05-08 18:37 ` [RFC PATCH 3/8] hw/pci: introduce allocator for fixed BAR placement Tushar Dave
2026-05-08 18:37 ` [RFC PATCH 4/8] hw/pci: pack remaining BARs and update bridge windows Tushar Dave
2026-05-08 18:37 ` [RFC PATCH 5/8] hw/pci: allocate remaining BARs for buses without fixed BARs Tushar Dave
2026-05-08 18:37 ` [RFC PATCH 6/8] hw/pci: finalize bridge prefetch windows after BAR allocation Tushar Dave
2026-05-08 18:37 ` [RFC PATCH 7/8] hw/arm/virt: add pcie-mmio-window machine property Tushar Dave
2026-05-08 18:37 ` [RFC PATCH 8/8] hw/arm/virt: add pci-pre-enum " Tushar Dave
2026-05-11 7:46 ` [RFC PATCH 0/8] hw/arm/virt, hw/pci: PCI pre-enumeration and fixed BAR allocation Peter Maydell
2026-05-11 12:26 ` Jason Gunthorpe
2026-05-11 18:38 ` Mohamed Mediouni
2026-05-11 20:28 ` Jason Gunthorpe
2026-05-11 9:09 ` Michael S. Tsirkin
2026-05-11 18:10 ` Tushar Dave
2026-05-11 22:09 ` Michael S. Tsirkin
2026-05-11 11:43 ` [edk2-devel] " Ard Biesheuvel
2026-05-12 17:25 ` Tushar Dave
2026-05-12 23:06 ` Alex Williamson
2026-05-12 23:12 ` Michael S. Tsirkin
2026-05-12 23:57 ` Alex Williamson
2026-05-13 11:36 ` Jason Gunthorpe
2026-05-13 14:25 ` Ard Biesheuvel
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=20260508183717.193630-1-tdave@nvidia.com \
--to=tdave@nvidia.com \
--cc=alwilliamson@nvidia.com \
--cc=devel@edk2.groups.io \
--cc=jgg@nvidia.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=skolothumtho@nvidia.com \
/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.