From: "Jonathan Cameron via groups.io" <jonathan.cameron=huawei.com@groups.io>
To: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Cc: Yuquan Wang <wangyuquan1236@phytium.com.cn>,
<devel@edk2.groups.io>, <ardb+tianocore@kernel.org>,
<quic_llindhol@quicinc.com>, <peter.maydell@linaro.org>,
<chenbaozi@phytium.com.cn>, <linux-cxl@vger.kernel.org>,
<asa-dev@op-lists.linaro.org>, <qemu-devel@nongnu.org>,
<qemu-arm@nongnu.org>
Subject: Re: [edk2-devel] [RFC PATCH v2 1/1] hw/arm/sbsa-ref: Support CXL Host Bridge & CFMW
Date: Thu, 21 Nov 2024 16:55:58 +0000 [thread overview]
Message-ID: <20241121165558.00005f1b@huawei.com> (raw)
In-Reply-To: <90513bfa-0888-44fe-8cd0-7b2e7518a41f@linaro.org>
On Tue, 12 Nov 2024 18:10:56 +0100
Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org> wrote:
> W dniu 7.11.2024 o 13:04, Jonathan Cameron pisze:
> > On Tue, 5 Nov 2024 18:43:46 +0800
> > "Yuquan Wang"<wangyuquan1236@phytium.com.cn> wrote:
> >
> >> This creates a default pxb-cxl (bus_nr=0xc0) bridge with two
> >> cxl root ports on sbsa-ref. And the memory layout places 64K
> >> space for the cxl host bridge register regions(CHBCR) in the
> >> sbsa-ref memmap.
> >>
> >> In addition, this support indepentent mmio32(32M) & mmio64(1M)
> >> space for cxl components.
>
> > Those are too small. Might work today but not sustainable.
> >
> > I'm a bit surprised it was this simple to move the MMIO Space away
> > from what is normally done for PXBs.
> > I think it might work because the GPEX memory windows are effectively
> > unlimited in size but I'd like some more eyes on this from people
> > familiar with how all that works and whether there might be some
> > corner cases that you haven't seen yet.
>
> I see the same problem as with multiple PCIe buses (for NUMA systems):
>
> pci 0000:c0:00.0: bridge window [io size 0x1000]: can't assign; no space
> pci 0000:c0:00.0: bridge window [io size 0x1000]: failed to assign
> pci 0000:c0:01.0: bridge window [io size 0x1000]: can't assign; no space
> pci 0000:c0:01.0: bridge window [io size 0x1000]: failed to assign
>
> I do not know how it looks on real hardware (all my systems have one
> PCIe bus) but shouldn't each host bridge have own separate resource
> windows for config space, buses, mmio etc.?
>
> Now we squeeze all pcie buses as pcie-pxb devices and this patch adds
> cxl to the combo.
In theory fine to break them up because each can have a smaller window
they just happen to be next to each other in this configuration.
CXL PXB (maybe the pcie one was well) doesn't IIRC support IO regions
in general. So that above is kind of normal and shouldn't matter
unless you emulate an ancient PCI device.
Jonathan
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120811): https://edk2.groups.io/g/devel/message/120811
Mute This Topic: https://groups.io/mt/109403514/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2024-11-21 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 10:43 [edk2-devel] [RFC PATCH v2 0/1] Sbsa-ref CXL Enablement Yuquan Wang
2024-11-05 10:43 ` [edk2-devel] [RFC PATCH v2 1/1] hw/arm/sbsa-ref: Support CXL Host Bridge & CFMW Yuquan Wang
2024-11-07 12:04 ` Jonathan Cameron via groups.io
2024-11-12 17:10 ` Marcin Juszkiewicz via groups.io
2024-11-21 16:55 ` Jonathan Cameron via groups.io [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-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=20241121165558.00005f1b@huawei.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