From: "Marcin Juszkiewicz" <marcin.juszkiewicz@linaro.org>
To: Ard Biesheuvel <ardb@kernel.org>, devel@edk2.groups.io
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, 4 Jun 2024 09:23:30 +0200 [thread overview]
Message-ID: <64916d39-c895-48a5-af9a-655c57233300@linaro.org> (raw)
In-Reply-To: <CAMj1kXGUgoDQcwyWPwHux8hYBGs+4tRWAt0-gqkGsV-X+gotRw@mail.gmail.com>
W dniu 28.05.2024 o 16:31, Ard Biesheuvel pisze:
> 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.
OK. I have to admit that I never checked how physical NUMA system
handles PCI Express. The code in patches was done by comparing with
other QEMU targets.
To make PCIe in a way you describe we probably need to go to QEMU devel
ML and discuss how it can be done there. Or I did not got deep enough
into PCIe world to notice how to make it happen with current implementation.
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#119442): https://edk2.groups.io/g/devel/message/119442
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-06-04 7:23 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 ` [edk2-devel] [PATCH edk2-platforms v2 0/3] SbsaQemu: support multiple PCI Express buses Ard Biesheuvel
2024-06-04 7:23 ` Marcin Juszkiewicz [this message]
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=64916d39-c895-48a5-af9a-655c57233300@linaro.org \
--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