From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: "Zhijian Li (Fujitsu)\" via <qemu-devel@nongnu.org>"@domain.invalid
Cc: "Zhijian Li (Fujitsu)" <lizhijian@fujitsu.com>,
Itaru Kitayama <itaru.kitayama@linux.dev>
Subject: Re: CXL emulation on aarch64
Date: Fri, 10 Jan 2025 12:31:28 +0000 [thread overview]
Message-ID: <20250110123128.00004a5b@huawei.com> (raw)
In-Reply-To: <483e8037-3c72-4560-b4b8-2437d37ca8c4@fujitsu.com>
On Fri, 10 Jan 2025 09:20:54 +0000
"Zhijian Li (Fujitsu)" via <qemu-devel@nongnu.org> wrote:
> On 10/01/2025 13:29, Itaru Kitayama wrote:
> > Hi,
> > Is anybody working on the CXL emulation on aarch64?
>
> I'm not currently working on the CXL emulation on aarch64.
>
> However, IIRC the CXL maintainer's tree should work.
> https://gitlab.com/jic23/qemu/
Pick up latest branch from there. I'm prepping a rebased version
with some new stuff but might take a few more days.
Note my main development work is on arm64 so that tends to work
more reliably than x86 which I only lightly test for stuff that
isn't ready for upstream yet.
Give me a shout if you run into any problems.
The main blocker on upstreaming this is resolving the missing device tree
support for PCI expander bridges. I've not made any progress on this since
talk at Linaro connect in 2023.
Jonathan
>
>
> Thanks
> Zhijian
>
> > If there’s a WIP branch, a pointer would be appreciated.
> >
> > Itaru
next prev parent reply other threads:[~2025-01-10 12:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 5:29 CXL emulation on aarch64 Itaru Kitayama
2025-01-10 9:20 ` Zhijian Li (Fujitsu) via
2025-01-10 12:31 ` Jonathan Cameron via [this message]
2025-01-14 3:03 ` Itaru Kitayama
2025-01-14 10:26 ` Jonathan Cameron via
2025-01-16 6:04 ` Itaru Kitayama
2025-01-16 10:58 ` Jonathan Cameron via
2025-01-17 0:24 ` Itaru Kitayama
2025-01-17 9:34 ` Jonathan Cameron via
2025-01-17 1:13 ` Itaru Kitayama
2025-01-17 9:43 ` Jonathan Cameron via
2025-01-22 14:07 ` Jonathan Cameron via
2025-01-29 1:14 ` Itaru Kitayama
2025-01-29 17:16 ` Jonathan Cameron via
2025-01-29 23:06 ` Itaru Kitayama
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=20250110123128.00004a5b@huawei.com \
--to=qemu-devel@nongnu.org \
--cc="Zhijian Li (Fujitsu)\" via <qemu-devel@nongnu.org>"@domain.invalid \
--cc=Jonathan.Cameron@huawei.com \
--cc=itaru.kitayama@linux.dev \
--cc=lizhijian@fujitsu.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.