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@memverge.com" <gregory.price@memverge.com>
Subject: Re: CXL Namespaces of ACPI disappearing in Qemu demo
Date: Wed, 6 Sep 2023 19:22:19 +0800 [thread overview]
Message-ID: <2023090619221880715697@phytium.com.cn> (raw)
In-Reply-To: 20230905153438.000075ff@huawei.com
[-- Attachment #1: Type: text/plain, Size: 861 bytes --]
Hi, Jonathan
On 2023-09-05 22:34, jonathan.cameron wrote:
>
> As I understand it the distinction is more about the format / contents of that memory
> than how you access them.
Yes, RCH DP RCRB includes registers from PCIe Type 1 Config Header and
PCIe capabilities and extended capabilities while CHBCR includes component registers
with the same layout and discovery mechanism in other CXL components.
> As an aside, they are described by a static ACPI table,
> so they can't be in the MMIO space used for BARs etc.
>
In CXL 3.0 Spec, the Figure 9-14 (CXL Link/Protocol Register Mapping in a CXL VH)
shows that CHBCR is mapped by "Host Proprietary Static Bar". According to your guidance,
it is not a standard PCIe BAR using PCIe MMIO Space, so I understand it is a special BAR for
MMIO of a platform device?
Many thanks
Yuquan
[-- Attachment #2: Type: text/html, Size: 2501 bytes --]
next prev parent reply other threads:[~2023-09-06 11:23 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
2023-09-05 14:34 ` Jonathan Cameron via
2023-09-05 14:34 ` Jonathan Cameron via
2023-09-06 11:22 ` Yuquan Wang [this message]
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=2023090619221880715697@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.