From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Stewart Hildebrand <stewart.hildebrand@amd.com>
Subject: Re: [PATCH v3 5/6] x86/PCI: avoid re-evaluation of extended config space accessibility
Date: Tue, 3 Feb 2026 18:19:03 +0100 [thread overview]
Message-ID: <aYIuB96SYzVwGfmj@Mac.lan> (raw)
In-Reply-To: <4913d9b3-03ec-443e-b908-a1531dca6699@suse.com>
On Tue, Feb 03, 2026 at 03:48:52PM +0100, Jan Beulich wrote:
> On 02.02.2026 16:18, Roger Pau Monné wrote:
> > My copy of the PCI Firmware Spec v3.3 contains:
> >
> > "4.1.2. MCFG Table Description
> >
> > The MCFG table is an ACPI table that is used to communicate the base
> > addresses corresponding to the non-hot removable PCI Segment Groups
> > range within a PCI Segment Group available to the operating system at
> > boot.
> >
> > [...]
> >
> > 4.1.3. The _CBA Method
> >
> > Some systems may support hot plug of host bridges that introduce
> > either a range of buses within an existing PCI Segment Group or
> > introduce a new PCI Segment Group. For example, each I/O chip in a
> > multi-chip PCI Express root complex implementation could start a new
> > PCI Segment Group."
> >
> > Together with this:
> >
> > "The MCFG table format allows for more than one memory mapped base
> > address entry provided each entry (memory mapped configuration space
> > base address allocation structure) corresponds to a unique PCI Segment
> > Group consisting of 256 PCI buses. Multiple entries corresponding to a
> > single PCI Segment Group is not allowed."
> >
> > Given that each segment group can only appear once in the MCFG, and
> > that the _CBA method can introduce new segment groups, it would seem
> > to me the spec does allow for new segments appearing exclusively as
> > the return of _CBA method? It does read as if hot-removable segment
> > groups must not appear in the MCFG table. I'm not finding any clear
> > statement in the spec that says that ECAM areas must previously appear
> > in the MCFG table.
> >
> > I'm not sure how common that is, but it doesn't seem impossible given
> > my reading of the spec.
>
> Hmm, that'll be a bit of work then, as Dom0 will also need to propagate
> the necessary data into Xen.
TBH this is what the spec says, but I've never encountered such a
system. In fact I've never tested hotplug of a PCI host bridge.
Not sure this can be simulated with QEMU so that we could at least
test whatever fixes we plan to do in that area? I guess we could
"fake" a bodge where Xen ignores the MCFG completely and only becomes
aware of the ECAM areas from what the hardware domain reports back.
Thanks, Roger.
next prev parent reply other threads:[~2026-02-03 17:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 13:05 [PATCH v3 0/6] (v)PCI: extended capability handling Jan Beulich
2026-01-29 13:07 ` [PATCH v3 1/6] PCI: handle PCI->PCIe bridges as well in free_pdev() Jan Beulich
2026-01-29 13:49 ` Roger Pau Monné
2026-01-29 13:08 ` [PATCH v3 2/6] PCI: determine whether a device has extended config space Jan Beulich
2026-01-29 14:09 ` Roger Pau Monné
2026-01-29 14:17 ` Jan Beulich
2026-02-02 9:14 ` Jan Beulich
2026-02-02 9:21 ` Roger Pau Monné
2026-01-29 13:08 ` [PATCH v3 3/6] PCI: don't look for ext-caps when there's no extended cfg space Jan Beulich
2026-01-29 13:09 ` [PATCH v3 4/6] vPCI: really no ext-caps without extended config space Jan Beulich
2026-01-29 14:13 ` Roger Pau Monné
2026-01-29 13:10 ` [PATCH v3 5/6] x86/PCI: avoid re-evaluation of extended config space accessibility Jan Beulich
2026-01-29 15:32 ` Roger Pau Monné
2026-01-29 15:47 ` Jan Beulich
2026-02-02 8:51 ` Jan Beulich
2026-02-02 9:14 ` Roger Pau Monné
2026-02-02 9:30 ` Jan Beulich
2026-02-02 10:13 ` Roger Pau Monné
2026-02-02 14:40 ` Jan Beulich
2026-02-02 15:18 ` Roger Pau Monné
2026-02-03 14:48 ` Jan Beulich
2026-02-03 17:19 ` Roger Pau Monné [this message]
2026-02-02 19:25 ` Stewart Hildebrand
2026-01-29 13:10 ` [PATCH v3 6/6] vPCI: re-init extended-capability lists when MMCFG availability changed Jan Beulich
2026-01-29 15:40 ` Roger Pau Monné
2026-01-29 15:54 ` Jan Beulich
2026-01-29 17:41 ` Roger Pau Monné
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=aYIuB96SYzVwGfmj@Mac.lan \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=stewart.hildebrand@amd.com \
--cc=xen-devel@lists.xenproject.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.