From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Fabiano Rosas" <farosas@suse.de>,
"Maciej S. Szmigiero" <maciej.szmigiero@oracle.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"David Hildenbrand" <david@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
kvm@vger.kernel.org, "Peter Xu" <peterx@redhat.com>
Subject: [PATCH 0/6] system/ramblock: Sanitize header
Date: Mon, 29 Sep 2025 17:45:23 +0200 [thread overview]
Message-ID: <20250929154529.72504-1-philmd@linaro.org> (raw)
Usual API cleanups, here focusing on RAMBlock API:
move few prototypes out of "exec/cpu-common.h" and
"system/ram_addr.h" to "system/ramblock.h".
Philippe Mathieu-Daudé (6):
system/ramblock: Remove obsolete comment
system/ramblock: Move ram_block_is_pmem() declaration
system/ramblock: Move ram_block_discard_*_range() declarations
system/ramblock: Use ram_addr_t in ram_block_discard_guest_memfd_range
system/ramblock: Use ram_addr_t in ram_block_discard_range()
system/ramblock: Move RAMBlock helpers out of "system/ram_addr.h"
include/exec/cpu-common.h | 3 --
include/system/ram_addr.h | 13 ------
include/system/ramblock.h | 27 +++++++++---
accel/kvm/kvm-all.c | 1 +
hw/hyperv/hv-balloon-our_range_memslots.c | 1 +
hw/virtio/virtio-balloon.c | 1 +
hw/virtio/virtio-mem.c | 1 +
migration/ram.c | 3 +-
system/physmem.c | 50 ++++++++++++-----------
9 files changed, 55 insertions(+), 45 deletions(-)
--
2.51.0
next reply other threads:[~2025-09-29 15:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 15:45 Philippe Mathieu-Daudé [this message]
2025-09-29 15:45 ` [PATCH 1/6] system/ramblock: Remove obsolete comment Philippe Mathieu-Daudé
2025-09-29 16:13 ` David Hildenbrand
2025-09-29 15:45 ` [PATCH 2/6] system/ramblock: Move ram_block_is_pmem() declaration Philippe Mathieu-Daudé
2025-09-29 16:58 ` Alex Bennée
2025-09-29 15:45 ` [PATCH 3/6] system/ramblock: Move ram_block_discard_*_range() declarations Philippe Mathieu-Daudé
2025-09-29 15:45 ` [PATCH 4/6] system/ramblock: Use ram_addr_t in ram_block_discard_guest_memfd_range Philippe Mathieu-Daudé
2025-10-01 15:59 ` Richard Henderson
2025-09-29 15:45 ` [PATCH 5/6] system/ramblock: Use ram_addr_t in ram_block_discard_range() Philippe Mathieu-Daudé
2025-09-29 15:45 ` [PATCH 6/6] system/ramblock: Move RAMBlock helpers out of "system/ram_addr.h" Philippe Mathieu-Daudé
2025-10-01 16:03 ` Richard Henderson
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=20250929154529.72504-1-philmd@linaro.org \
--to=philmd@linaro.org \
--cc=david@redhat.com \
--cc=farosas@suse.de \
--cc=kvm@vger.kernel.org \
--cc=maciej.szmigiero@oracle.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).