From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Maverickk 78 <maverickk1778@gmail.com>,
Igor Mammedov <imammedo@redhat.com>,
David Hildenbrand <david@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: CXL volatile memory is not listed
Date: Thu, 10 Aug 2023 12:59:28 +0200 [thread overview]
Message-ID: <f64d5006-ae77-cc10-270a-0c0fc6e3a0ef@linaro.org> (raw)
In-Reply-To: <CALfBBTtUtydebmJuh6JZ5RAXZfx5OgJ+RCug1apbZa4mm17rJQ@mail.gmail.com>
Hi,
Cc'ing Igor and David.
On 9/8/23 00:51, Maverickk 78 wrote:
> Hello,
>
> I am running qemu-system-x86_64
>
> qemu-system-x86_64 --version
> QEMU emulator version 8.0.92 (v8.1.0-rc2-80-g0450cf0897)
>
> qemu-system-x86_64 \
> -m 2G,slots=4,maxmem=4G \
> -smp 4 \
> -machine type=q35,accel=kvm,cxl=on \
> -enable-kvm \
> -nographic \
> -device pxb-cxl,id=cxl.0,bus=pcie.0,bus_nr=52 \
> -device cxl-rp,id=rp0,bus=cxl.0,chassis=0,port=0,slot=0 \
> -object memory-backend-file,id=mem0,mem-path=/tmp/mem0,size=1G,share=true \
> -device cxl-type3,bus=rp0,volatile-memdev=mem0,id=cxl-mem0 \
> -M cxl-fmw.0.targets.0=cxl.0,cxl-fmw.0.size=1G
>
>
> I was expecting the CXL memory to be listed in "System Ram", the lsmem
> shows only 2G memory which is System RAM, it's not listing the CXL
> memory.
Sounds like a bug. Do you mind reporting at
https://gitlab.com/qemu-project/qemu/-/issues?
Thanks,
Phil.
> Do I need to pass any particular parameter in the kernel command line?
>
> Is there any documentation available? I followed the inputs provided in
>
> https://lore.kernel.org/linux-mm/Y+CSOeHVLKudN0A6@kroah.com/T/
>
> Is there any documentation/blog listed?
>
next prev parent reply other threads:[~2023-08-10 11:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 22:51 CXL volatile memory is not listed Maverickk 78
2023-08-10 10:35 ` Jonathan Cameron via
2023-08-11 2:34 ` Maverickk 78
2023-08-11 13:54 ` Jonathan Cameron via
2023-08-18 5:18 ` Maverickk 78
2023-08-18 11:30 ` Shreyas Shah via
2023-08-23 16:59 ` Jonathan Cameron via
2023-08-23 17:02 ` Jonathan Cameron via
2023-08-10 10:59 ` Philippe Mathieu-Daudé [this message]
2023-08-10 11:18 ` David Hildenbrand
2023-08-11 2:42 ` Maverickk 78
2023-08-10 16:32 ` Fan Ni
2023-08-11 2:22 ` Maverickk 78
2023-08-11 16:48 ` Fan Ni
2023-08-18 5:05 ` Maverickk 78
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=f64d5006-ae77-cc10-270a-0c0fc6e3a0ef@linaro.org \
--to=philmd@linaro.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=david@redhat.com \
--cc=imammedo@redhat.com \
--cc=maverickk1778@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).