From: "Yuquan Wang" <wangyuquan1236@phytium.com.cn>
To: jonathan.cameron <Jonathan.Cameron@Huawei.com>
Cc: qemu-arm <qemu-arm@nongnu.org>,
qemu-devel <qemu-devel@nongnu.org>,
gregory.price <gregory.price@memverge.com>
Subject: Re: CXL Namespaces of ACPI disappearing in Qemu demo
Date: Tue, 5 Sep 2023 18:45:02 +0800 [thread overview]
Message-ID: <2023090518450211126476@phytium.com.cn> (raw)
In-Reply-To: 20230904134342.000048bf@Huawei.com
[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]
Hi, Jonathan
On 2023-09-04 20:43, jonathan.cameron wrote:
>
> At the system design level, MMIO space of Root complex register space via RCRB
> does not map in a similar fashion to PCIE MMIO space (which is handled via
> address decoding in the PCIE fabric). It is much more similar to MMIO for platform
> devices - as such the implementation handles in like a platform device (well 16 of
> them which seemed enough for any sane usecase).
>
>
Oh,thanks! According to above, therefore, the core factor is the implementation of RCRB.
>
> So in theory we could make some space for the CXL root bridge RCRB registers
> but it would make various generic paths more complex. In a real system
> those registers are likely to be far from the PCI MMIO space anyway so the
> way it's modeled is probably more realistic than pushing the RCRB into the
> existing allocation.
>
Here implies that all CXL root bridge will use RCRB registers.
From Table 8-17 and Figure 9-14 in CXL3.0 specification, I understood that only RCH DP &
RCD UP will use RCRBs, and CXL host bridges VH mode will use other way to realize
the CHBCR. I had tried to find more explanation in CXL spec, but I haven't found. Hence
this is why I am confused.
Many thanks
Yuquan
[-- Attachment #2: Type: text/html, Size: 2493 bytes --]
next prev parent reply other threads:[~2023-09-05 10:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 7:22 CXL Namespaces of ACPI disappearing in Qemu demo Yuquan Wang
2023-08-23 19:44 ` Gregory Price
2023-08-24 1:11 ` Yuquan Wang
2023-08-24 9:06 ` Jonathan Cameron via
2023-09-04 10:27 ` Yuquan Wang
2023-09-04 12:43 ` Jonathan Cameron via
2023-09-04 12:43 ` Jonathan Cameron via
2023-09-05 10:45 ` Yuquan Wang [this message]
2023-09-05 14:34 ` Jonathan Cameron via
2023-09-05 14:34 ` Jonathan Cameron via
2023-09-06 11:22 ` Yuquan Wang
2023-09-07 10:58 ` Jonathan Cameron via
2023-09-07 10:58 ` Jonathan Cameron via
[not found] ` <2023092018244461102314@phytium.com.cn>
2023-09-20 12:19 ` A confusion about cxl.mem in CXL drivers Jonathan Cameron
2023-09-22 8:49 ` Yuquan Wang
-- strict thread matches above, loose matches on Subject: below --
2023-06-16 7:43 A confusion about CXL in arm virt machine Yuquan Wang
2023-06-16 18:10 ` Gregory Price
2023-06-19 9:58 ` Jonathan Cameron via
2023-08-10 9:30 ` CXL Namespaces of ACPI disappearing in Qemu demo Yuquan Wang
2023-08-10 10:04 ` Jonathan Cameron via
2023-08-10 13:56 ` Jonathan Cameron via
2023-08-11 10:31 ` Yuquan Wang
2023-08-22 15:23 ` Jonathan Cameron via
2023-08-22 15:23 ` Jonathan Cameron via
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=2023090518450211126476@phytium.com.cn \
--to=wangyuquan1236@phytium.com.cn \
--cc=Jonathan.Cameron@Huawei.com \
--cc=gregory.price@memverge.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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.