From: Maverickk 78 <maverickk1778@gmail.com>
To: Jonathan Cameron via <qemu-devel@nongnu.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: CXL volatile memory is not listed
Date: Wed, 9 Aug 2023 04:21:47 +0530 [thread overview]
Message-ID: <CALfBBTtUtydebmJuh6JZ5RAXZfx5OgJ+RCug1apbZa4mm17rJQ@mail.gmail.com> (raw)
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.
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 reply other threads:[~2023-08-08 22:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 22:51 Maverickk 78 [this message]
2023-08-10 10:35 ` CXL volatile memory is not listed 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é
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=CALfBBTtUtydebmJuh6JZ5RAXZfx5OgJ+RCug1apbZa4mm17rJQ@mail.gmail.com \
--to=maverickk1778@gmail.com \
--cc=Jonathan.Cameron@huawei.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).