From: "Ard Biesheuvel" <ardb@kernel.org>
To: devel@edk2.groups.io, marcin.juszkiewicz@linaro.org
Cc: Leif Lindholm <quic_llindhol@quicinc.com>,
Graeme Gregory <graeme@xora.org.uk>, Ray Ni <ray.ni@intel.com>
Subject: Re: [edk2-devel] [PATCH edk2-platforms v2 0/3] SbsaQemu: support multiple PCI Express buses
Date: Tue, 28 May 2024 16:31:06 +0200 [thread overview]
Message-ID: <CAMj1kXGUgoDQcwyWPwHux8hYBGs+4tRWAt0-gqkGsV-X+gotRw@mail.gmail.com> (raw)
In-Reply-To: <20240528-review-multiple-pcie-0425-v2-0-e2ec9f098a78@linaro.org>
On Tue, 28 May 2024 at 12:31, Marcin Juszkiewicz
<marcin.juszkiewicz@linaro.org> wrote:
>
> QEMU allows to have NUMA setup where each node has own cpus, memory and
> i/o. We already handle cpus and memory. This patchset adds support for
> having multiple PCI Express buses.
>
> SbsaQemu assumed that there is only bus 0. First patch does PCIe bus
> scan to find all host bridges (bus 0 one and additional 'pxb-pcie'
> ones).
>
> Second patch moves description of PCIe from DSDT to SSDT (one per each
> PCIe bus). So Operating System will know about all of them.
>
> Third patch moves generation of MCFG table to C. It is preparation to
> move PCIe Pcds from being fixed to dynamic ones.
>
> There are some booting issues with assigning resources for cards:
>
> pci 0000:00:03.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
> pci 0000:00:03.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
> pci 0000:00:01.0: BAR 6: no space for [mem size 0x00040000 pref]
> pci 0000:00:01.0: BAR 6: failed to assign [mem size 0x00040000 pref]
> pci 0000:00:03.0: BAR 13: no space for [io size 0x1000]
> pci 0000:00:03.0: BAR 13: failed to assign [io size 0x1000]
>
> Boot log (Linux + lspci + ACPI tables dump):
> https://people.linaro.org/~marcin.juszkiewicz/sbsa-ref/boot-linux-with-numa-multiple-pcie-buses.txt
>
> I am wondering where I made mistakes in handling PCIe buses.
>
I would expect each host bridge to have its own separate resource
windows for config space, buses and MMIO regions.
So each host bridge gets a different segment number, and each segment
is associated with a different ECAM region. That also means the bus
range can start at 0x0 for each segment, as they are completely
disjoint.
This is a more accurate representation of the physical topology, given
that each host bridge has its own link to the CPU side interconnect,
and so things like peer-to-peer DMA between endpoints does not
generally work unless the endpoints share a segment, especially in the
presence of SMMUs.
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#119308): https://edk2.groups.io/g/devel/message/119308
Mute This Topic: https://groups.io/mt/106345969/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-05-28 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 10:31 [edk2-devel] [PATCH edk2-platforms v2 0/3] SbsaQemu: support multiple PCI Express buses Marcin Juszkiewicz
2024-05-28 10:31 ` [edk2-devel] [PATCH edk2-platforms v2 1/3] SbsaQemu: scan for PCIe buses Marcin Juszkiewicz
2024-05-28 10:31 ` [edk2-devel] [PATCH edk2-platforms v2 2/3] SbsaQemu: describe PCIe buses in SSDT tables Marcin Juszkiewicz
2024-05-28 10:31 ` [edk2-devel] [PATCH edk2-platforms v2 3/3] SbsaQemu: generate MCFG table Marcin Juszkiewicz
2024-05-28 14:31 ` Ard Biesheuvel [this message]
2024-06-04 7:23 ` [edk2-devel] [PATCH edk2-platforms v2 0/3] SbsaQemu: support multiple PCI Express buses Marcin Juszkiewicz
2024-06-04 12:06 ` Gerd Hoffmann
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-list 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=CAMj1kXGUgoDQcwyWPwHux8hYBGs+4tRWAt0-gqkGsV-X+gotRw@mail.gmail.com \
--to=devel@edk2.groups.io \
/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