From: David Hildenbrand <david@redhat.com>
To: "Ho-Ren (Jack) Chuang" <horenchuang@bytedance.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Hao Xiang" <hao.xiang@bytedance.com>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
"Ben Widawsky" <ben.widawsky@intel.com>,
"Gregory Price" <gourry.memverge@gmail.com>,
"Fan Ni" <fan.ni@samsung.com>, "Ira Weiny" <ira.weiny@intel.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Igor Mammedov" <imammedo@redhat.com>,
"Eric Blake" <eblake@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
qemu-devel@nongnu.org
Cc: "Ho-Ren (Jack) Chuang" <horenc@vt.edu>, linux-cxl@vger.kernel.org
Subject: Re: [QEMU-devel][RFC PATCH 1/1] backends/hostmem: qapi/qom: Add an ObjectOption for memory-backend-* called HostMemType and its arg 'cxlram'
Date: Tue, 2 Jan 2024 14:03:54 +0100 [thread overview]
Message-ID: <3ecd3b5a-c4d3-4fd5-b75b-d89b1d4b45e5@redhat.com> (raw)
In-Reply-To: <20240101075315.43167-2-horenchuang@bytedance.com>
On 01.01.24 08:53, Ho-Ren (Jack) Chuang wrote:
> Introduce a new configuration option 'host-mem-type=' in the
> '-object memory-backend-ram', allowing users to specify
> from which type of memory to allocate.
>
> Users can specify 'cxlram' as an argument, and QEMU will then
> automatically locate CXL RAM NUMA nodes and use them as the backend memory.
> For example:
> -object memory-backend-ram,id=vmem0,size=19G,host-mem-type=cxlram \
> -device pxb-cxl,bus_nr=12,bus=pcie.0,id=cxl.1 \
> -device cxl-rp,port=0,bus=cxl.1,id=root_port13,chassis=0,slot=2 \
> -device cxl-type3,bus=root_port13,volatile-memdev=vmem0,id=cxl-vmem0 \
> -M cxl-fmw.0.targets.0=cxl.1,cxl-fmw.0.size=19G,cxl-fmw.0.interleave-granularity=8k \
>
You can achieve the exact same thing already simply by using memory
policies and detecting the node(s) before calling QEMU, no?
There has to be a good reason to add such a shortcut into QEMU, and it
should be spelled out here.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-01-02 13:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-01 7:53 [QEMU-devel][RFC PATCH 0/1] Introduce HostMemType for 'memory-backend-*' Ho-Ren (Jack) Chuang
2024-01-01 7:53 ` [QEMU-devel][RFC PATCH 1/1] backends/hostmem: qapi/qom: Add an ObjectOption for memory-backend-* called HostMemType and its arg 'cxlram' Ho-Ren (Jack) Chuang
2024-01-02 10:29 ` Philippe Mathieu-Daudé
2024-01-02 13:03 ` David Hildenbrand [this message]
2024-01-06 0:45 ` [External] " Hao Xiang
2024-01-03 21:56 ` Gregory Price
2024-01-06 5:59 ` [External] " Hao Xiang
2024-01-08 17:15 ` Gregory Price
2024-01-08 22:47 ` Hao Xiang
2024-01-09 1:05 ` Hao Xiang
2024-01-09 1:13 ` Gregory Price
2024-01-09 19:33 ` Hao Xiang
2024-01-09 19:57 ` Gregory Price
2024-01-09 21:27 ` Hao Xiang
2024-01-09 22:13 ` Gregory Price
2024-01-09 23:55 ` Hao Xiang
2024-01-10 14:31 ` Jonathan Cameron via
2024-01-12 15:32 ` Markus Armbruster
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=3ecd3b5a-c4d3-4fd5-b75b-d89b1d4b45e5@redhat.com \
--to=david@redhat.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=armbru@redhat.com \
--cc=ben.widawsky@intel.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=eduardo@habkost.net \
--cc=fan.ni@samsung.com \
--cc=gourry.memverge@gmail.com \
--cc=hao.xiang@bytedance.com \
--cc=horenc@vt.edu \
--cc=horenchuang@bytedance.com \
--cc=imammedo@redhat.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--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).