From: Gregory Price <gourry@gourry.net>
To: Hongjian Fan <hongjian.fan@seagate.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"fan.ni@samsung.com" <fan.ni@samsung.com>
Subject: Re: [PATCH] hw/mem: support zero memory size CXL device
Date: Tue, 10 Dec 2024 14:13:29 -0500 [thread overview]
Message-ID: <Z1iS2SeYSOQqdLVU@PC2K9PVX.TheFacebook.com> (raw)
In-Reply-To: <CH0PR20MB42505D4F82D534A85EEA4C2A90362@CH0PR20MB4250.namprd20.prod.outlook.com>
On Tue, Dec 03, 2024 at 09:15:51PM +0000, Hongjian Fan wrote:
> Hi Jonathan,
>
> I'm trying to emulate our memory appliance which is similar to a MH-SLD. The memory device is connected to the host server while the size of the memory could be changed by the out-of-band fabric manager. If there is no memory assigned to the host, the CXL device will be booted as zero memory size.
This should not be how this is done.
The ACPI tables should report the maximum possible size, and the DCD
infrastructure should enable physical regions that have been added to the host.
Changing ACPI tables to report 0 memory size will basically result
in the host memory map not reserving physical memory regions for that
device.
See this emulation example of an MHSLD - which can be used for DCD.
https://lore.kernel.org/linux-cxl/20241018161252.8896-1-gourry@gourry.net/
> Recently we got some interest on trying our fabric manager software without having the real hardware. Supporting zero memory size in QEMU will be needed in this scenario.
> Some detail about our memory appliance could be found from our OCP presentation: https://drive.google.com/file/d/1i8kBsBfRGjNqnTQqJ9upC-Xm9o56Y2Y5/view?usp=drive_link
>
> Thanks,
> Hongjian Fan
>
>
> Seagate Internal
next prev parent reply other threads:[~2024-12-10 19:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 23:03 [PATCH] hw/mem: support zero memory size CXL device Hongjian Fan
2024-12-03 17:23 ` Jonathan Cameron
2024-12-03 21:15 ` Hongjian Fan
2024-12-10 19:13 ` Gregory Price [this message]
2024-12-24 15:13 ` Jonathan Cameron
2025-01-23 15:23 ` Gregory Price
2024-12-04 2:26 ` [PATCH v2] " Hongjian Fan
2025-01-21 16:24 ` Jonathan Cameron
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=Z1iS2SeYSOQqdLVU@PC2K9PVX.TheFacebook.com \
--to=gourry@gourry.net \
--cc=Jonathan.Cameron@huawei.com \
--cc=fan.ni@samsung.com \
--cc=hongjian.fan@seagate.com \
--cc=linux-cxl@vger.kernel.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