From: Yuquan Wang <wangyuquan1236@phytium.com.cn>
To: Jonathan Cameron <jonathan.cameron@huawei.com>
Cc: rad@semihalf.com, peter.maydell@linaro.org,
leif.lindholm@oss.qualcomm.com, chenbaozi@phytium.com.cn,
qemu-devel@nongnu.org, linux-cxl@vger.kernel.org,
qemu-arm@nongnu.org, ligen@phytium.com.cn
Subject: Re: [RFC QEMU PATCH v7] hw/arm/sbsa-ref: Support CXL Host Bridge & CFMW
Date: Thu, 18 Sep 2025 11:10:38 +0800 [thread overview]
Message-ID: <aMt4LqSympNcVqnb@phytium.com.cn> (raw)
In-Reply-To: <20250917173914.0000331e@huawei.com>
On Wed, Sep 17, 2025 at 05:39:14PM +0100, Jonathan Cameron wrote:
> On Thu, 7 Aug 2025 19:10:37 +0800
> wangyuquan <wangyuquan1236@phytium.com.cn> wrote:
>
> > From: Yuquan Wang <wangyuquan1236@phytium.com.cn>
> >
> > This creates a specific CXL host bridge (0001:00) with four cxl
> > root ports on sbsa-ref. And the memory layout provides separate
> > space windows for the cxl host bridge in the sbsa-ref memmap:
> >
> > - 64K CXL Host Bridge Component Registers (CHBCR)
> > - 64K CXL_PIO
> > - 128M CXL_MMIO
> > - 256M CXL_ECAM
> > - 4G CXL_MMIO_HIGH
> >
> > To provide CFMWs on sbsa-ref, this extends 1TB space from the
> > hole above RAM Memory [SBSA_MEM] for CXL Fixed Memory Window:
> >
> > - 1T CXL_FIXED_WINDOW
> >
> > Signed-off-by: Yuquan Wang <wangyuquan1236@phytium.com.cn>
> This looks pretty standard to me so FWIW as someone who hasn't used
> the SBSA model.
>
> Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com>
>
>
Hi, Leif and SBSA folks
We hope to hear from everyone regarding other suggestions for using the
CXL on the sbsa-ref, as well as any areas where this patch might have
been overlooked.
Yuquan
prev parent reply other threads:[~2025-09-18 3:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 11:10 [RFC QEMU PATCH v7] hw/arm/sbsa-ref: Support CXL Host Bridge & CFMW wangyuquan
2025-09-17 16:39 ` Jonathan Cameron
2025-09-17 16:39 ` Jonathan Cameron via
2025-09-17 16:39 ` Jonathan Cameron via
2025-09-18 3:10 ` Yuquan Wang [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-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=aMt4LqSympNcVqnb@phytium.com.cn \
--to=wangyuquan1236@phytium.com.cn \
--cc=chenbaozi@phytium.com.cn \
--cc=jonathan.cameron@huawei.com \
--cc=leif.lindholm@oss.qualcomm.com \
--cc=ligen@phytium.com.cn \
--cc=linux-cxl@vger.kernel.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rad@semihalf.com \
/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.