From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Junjie Fu <fujunjie1@qq.com>
Cc: <qemu-devel@nongnu.org>, <linux-cxl@vger.kernel.org>,
<viacheslav.dubeyko@bytedance.com>, <zhitingz@cs.utexas.edu>,
Gregory Price <gourry@gourry.net>, <svetly.todorov@memverge.com>
Subject: Re: CXL memory pooling emulation inqury
Date: Wed, 12 Mar 2025 18:05:43 +0000 [thread overview]
Message-ID: <20250312180543.00002132@huawei.com> (raw)
In-Reply-To: <tencent_E9F3F01E0D2303378E16505CE4CF208AA908@qq.com>
On Mon, 10 Mar 2025 16:02:45 +0800
Junjie Fu <fujunjie1@qq.com> wrote:
> > Note though that there is a long way to go before we can do what you
> > want. The steps I'd expect to see along the way:
> >
> > 1) Emulate an Multi Headed Device.
> > Initially connect two heads to different host bridges on a single QEMU
> > machine. That lets us test most of the code flows without needing
> > to handle tests that involve multiple machines.
> > Later, we could add a means to connect between two instances of QEMU.
> > 2) Add DCD support (we'll need the kernel side of that as well)
> > 3) Wire it all up.
> > 4) Do the same for a Switch with MLDs behind it so we can poke the fun
> > corners.
>
>
> Hi,Jonathan
>
> Given your previous exploration, I would like to ask the following questions:
> 1.Does QEMU currently support simulating the above CXL memory pooling scenario?
Not in upstream yet but Gregory posted emulation support last year.
https://lore.kernel.org/qemu-devel/20241018161252.8896-1-gourry@gourry.net/
I'm carrying the patches on my staging tree.
https://gitlab.com/jic23/qemu/-/commits/cxl-2025-02-20?ref_type=heads
Longer term I remain a little unconvinced by whether this is the best approach
because I also want a single management path (so fake CCI etc) and that may
need to be exposed to one of the hosts for tests purposes. In the current
approach commands are issued to each host directly to surface memory.
>
> 2.If not fully supported yet, are there any available development branches
> or patches that implement this functionality?
>
> 3.Are there any guidelines or considerations for configuring and testing CXL memory pooling in QEMU?
There is some information in that patch series cover letter.
+CC Gregory and Svelty.
>
> I sincerely appreciate your time and guidance on this topic!
>
No problem.
Jonathan
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: Junjie Fu <fujunjie1@qq.com>
Cc: <qemu-devel@nongnu.org>, <linux-cxl@vger.kernel.org>,
<viacheslav.dubeyko@bytedance.com>, <zhitingz@cs.utexas.edu>,
Gregory Price <gourry@gourry.net>, <svetly.todorov@memverge.com>
Subject: Re: CXL memory pooling emulation inqury
Date: Wed, 12 Mar 2025 18:05:43 +0000 [thread overview]
Message-ID: <20250312180543.00002132@huawei.com> (raw)
In-Reply-To: <tencent_E9F3F01E0D2303378E16505CE4CF208AA908@qq.com>
On Mon, 10 Mar 2025 16:02:45 +0800
Junjie Fu <fujunjie1@qq.com> wrote:
> > Note though that there is a long way to go before we can do what you
> > want. The steps I'd expect to see along the way:
> >
> > 1) Emulate an Multi Headed Device.
> > Initially connect two heads to different host bridges on a single QEMU
> > machine. That lets us test most of the code flows without needing
> > to handle tests that involve multiple machines.
> > Later, we could add a means to connect between two instances of QEMU.
> > 2) Add DCD support (we'll need the kernel side of that as well)
> > 3) Wire it all up.
> > 4) Do the same for a Switch with MLDs behind it so we can poke the fun
> > corners.
>
>
> Hi,Jonathan
>
> Given your previous exploration, I would like to ask the following questions:
> 1.Does QEMU currently support simulating the above CXL memory pooling scenario?
Not in upstream yet but Gregory posted emulation support last year.
https://lore.kernel.org/qemu-devel/20241018161252.8896-1-gourry@gourry.net/
I'm carrying the patches on my staging tree.
https://gitlab.com/jic23/qemu/-/commits/cxl-2025-02-20?ref_type=heads
Longer term I remain a little unconvinced by whether this is the best approach
because I also want a single management path (so fake CCI etc) and that may
need to be exposed to one of the hosts for tests purposes. In the current
approach commands are issued to each host directly to surface memory.
>
> 2.If not fully supported yet, are there any available development branches
> or patches that implement this functionality?
>
> 3.Are there any guidelines or considerations for configuring and testing CXL memory pooling in QEMU?
There is some information in that patch series cover letter.
+CC Gregory and Svelty.
>
> I sincerely appreciate your time and guidance on this topic!
>
No problem.
Jonathan
next prev parent reply other threads:[~2025-03-12 18:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 22:28 CXL 2.0 memory pooling emulation zhiting zhu
2023-02-15 15:18 ` Jonathan Cameron via
2023-02-15 9:10 ` Gregory Price
2023-02-16 18:00 ` Jonathan Cameron via
2023-02-16 20:52 ` Gregory Price
2023-02-17 11:14 ` Jonathan Cameron via
2023-02-17 11:02 ` Gregory Price
2025-03-10 8:02 ` CXL memory pooling emulation inqury Junjie Fu
2025-03-12 18:05 ` Jonathan Cameron [this message]
2025-03-12 18:05 ` Jonathan Cameron via
2025-03-12 19:33 ` Gregory Price
2025-03-13 16:03 ` Fan Ni
2025-04-08 4:47 ` Fan Ni
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=20250312180543.00002132@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=fujunjie1@qq.com \
--cc=gourry@gourry.net \
--cc=linux-cxl@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=svetly.todorov@memverge.com \
--cc=viacheslav.dubeyko@bytedance.com \
--cc=zhitingz@cs.utexas.edu \
/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.