From: Peter Xu <peterx@redhat.com>
To: Xiaoyao Li <xiaoyao.li@intel.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"BALATON Zoltan" <balaton@eik.bme.hu>,
chenyi.qiang@intel.com, "Farrah Chen" <farrah.chen@intel.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH] memory: Set mr->ram before RAM Block allocation
Date: Thu, 12 Mar 2026 11:46:56 -0400 [thread overview]
Message-ID: <abLf8EW3M7XCBh2K@x1.local> (raw)
In-Reply-To: <20260312063420.973637-1-xiaoyao.li@intel.com>
On Thu, Mar 12, 2026 at 02:34:20PM +0800, Xiaoyao Li wrote:
> Commit 2fb627ef2f48 ("memory: Factor out common ram region initialization")
> introduced a helper function memory_region_set_ram_block(), which causes
> mr->ram to be set to true after the RAM Block allocation by
> qemu_ram_alloc_*().
>
> It leads to the assertion
>
> g_assert(memory_region_is_ram(mr));
>
> in memory_region_set_ram_discard_manager() being triggered when creating
> RAM Block with the RAM_GUEST_MEMFD flag.
>
> Fix this by restoring the original behavior of setting mr->ram before
> RAM Block allocation.
>
> Closes: https://gitlab.com/qemu-project/qemu/-/work_items/3330
> Reported-by: Farrah Chen <farrah.chen@intel.com>
> Fixes: 2fb627ef2f48 ("memory: Factor out common ram region initialization")
> Signed-off-by: Xiaoyao Li <xiaoyao.li@intel.com>
Thanks for the report. This is fast..
Almost agreed with the fix, except that it duplicates the lines all over
the places. Would it be better to introduce memory_region_init_ram()?
> ---
> system/memory.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/system/memory.c b/system/memory.c
> index 17a7bcd9af7c..56f3225b21ad 100644
> --- a/system/memory.c
> +++ b/system/memory.c
> @@ -1578,7 +1578,6 @@ void memory_region_init_io(MemoryRegion *mr, Object *owner,
>
> static bool memory_region_set_ram_block(MemoryRegion *mr, RAMBlock *rb)
> {
> - mr->ram = true;
> mr->terminates = true;
> mr->destructor = memory_region_destructor_ram;
> mr->ram_block = rb;
> @@ -1597,6 +1596,7 @@ bool memory_region_init_ram_flags_nomigrate(MemoryRegion *mr, Object *owner,
> RAMBlock *rb;
>
> memory_region_init(mr, owner, name, size);
> + mr->ram = true;
> rb = qemu_ram_alloc(size, ram_flags, mr, errp);
> return memory_region_set_ram_block(mr, rb);
> }
> @@ -1614,6 +1614,7 @@ bool memory_region_init_resizeable_ram(MemoryRegion *mr,
> RAMBlock *rb;
>
> memory_region_init(mr, owner, name, size);
> + mr->ram = true;
> rb = qemu_ram_alloc_resizeable(size, max_size, resized, mr, errp);
> return memory_region_set_ram_block(mr, rb);
> }
> @@ -1628,6 +1629,7 @@ bool memory_region_init_ram_from_file(MemoryRegion *mr, Object *owner,
> RAMBlock *rb;
>
> memory_region_init(mr, owner, name, size);
> + mr->ram = true;
> mr->readonly = !!(ram_flags & RAM_READONLY);
> mr->align = align;
> rb = qemu_ram_alloc_from_file(size, mr, ram_flags, path, offset, errp);
> @@ -1642,6 +1644,7 @@ bool memory_region_init_ram_from_fd(MemoryRegion *mr, Object *owner,
> RAMBlock *rb;
>
> memory_region_init(mr, owner, name, size);
> + mr->ram = true;
> mr->readonly = !!(ram_flags & RAM_READONLY);
> rb = qemu_ram_alloc_from_fd(size, size, NULL, mr, ram_flags, fd, offset,
> false, errp);
> @@ -1663,6 +1666,7 @@ void memory_region_init_ram_ptr(MemoryRegion *mr, Object *owner,
> void *ptr)
> {
> memory_region_init(mr, owner, name, size);
> + mr->ram = true;
> memory_region_set_ram_ptr(mr, size, ptr);
> }
>
> @@ -1671,6 +1675,7 @@ void memory_region_init_ram_device_ptr(MemoryRegion *mr, Object *owner,
> void *ptr)
> {
> memory_region_init_io(mr, owner, &ram_device_mem_ops, mr, name, size);
> + mr->ram = true;
> mr->ram_device = true;
> memory_region_set_ram_ptr(mr, size, ptr);
> }
> @@ -3699,7 +3704,6 @@ bool memory_region_init_rom_device(MemoryRegion *mr, Object *owner,
> memory_region_init_io(mr, owner, ops, opaque, name, size);
> rb = qemu_ram_alloc(size, 0, mr, errp);
> if (memory_region_set_ram_block(mr, rb)) {
> - mr->ram = false;
> mr->rom_device = true;
> memory_region_register_ram(mr, owner);
> return true;
> --
> 2.43.0
>
--
Peter Xu
next prev parent reply other threads:[~2026-03-12 15:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 6:34 [PATCH] memory: Set mr->ram before RAM Block allocation Xiaoyao Li
2026-03-12 15:46 ` Peter Xu [this message]
2026-03-12 18:04 ` BALATON Zoltan
2026-03-12 18:40 ` Peter Xu
2026-03-12 18:50 ` BALATON Zoltan
2026-03-13 3:36 ` Xiaoyao Li
2026-03-13 14:19 ` Peter Xu
2026-03-12 18:42 ` BALATON Zoltan
2026-03-17 23:38 ` Kim Phillips
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=abLf8EW3M7XCBh2K@x1.local \
--to=peterx@redhat.com \
--cc=balaton@eik.bme.hu \
--cc=chenyi.qiang@intel.com \
--cc=farrah.chen@intel.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=xiaoyao.li@intel.com \
/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.