From: Isaku Yamahata <isaku.yamahata@intel.com>
To: qemu-devel@nongnu.org
Cc: Isaku Yamahata <isaku.yamahata@intel.com>
Subject: [PATCH 0/3] Add symbols for memory listener priority
Date: Tue, 20 Jun 2023 09:50:46 -0700 [thread overview]
Message-ID: <cover.1687279702.git.isaku.yamahata@intel.com> (raw)
The hard-coded value, 10, is used for memory_listener_register(). Add symbolic
values for priority of struct MemoryLister. Replace those hard-coded values
with symbols.
The background is KVM guest memory[1] or TDX support. I'd like to add one more
memory listener whose priority is higher than the KVM memory listener. And I
don't want to hard-code 10 + 1.
[1] KVM gmem patches
https://github.com/sean-jc/linux/tree/x86/kvm_gmem_solo
Isaku Yamahata (3):
exec/memory: Add symbolic value for memory listener priority for accel
exec/memory: Add symbol for memory listener priority for dev backend
exec/memory: Add symbol for the min value of memory listener priority
accel/hvf/hvf-accel-ops.c | 2 +-
accel/kvm/kvm-all.c | 5 +++--
hw/arm/xen_arm.c | 2 +-
hw/i386/xen/xen-hvm.c | 2 +-
hw/remote/proxy-memory-listener.c | 2 +-
hw/virtio/vhost.c | 2 +-
hw/xen/xen-hvm-common.c | 2 +-
hw/xen/xen_pt.c | 4 ++--
include/exec/memory.h | 4 ++++
target/arm/kvm.c | 1 +
target/i386/hax/hax-mem.c | 2 +-
target/i386/nvmm/nvmm-all.c | 2 +-
target/i386/whpx/whpx-all.c | 2 +-
13 files changed, 19 insertions(+), 13 deletions(-)
base-commit: cab35c73be9d579db105ef73fa8a60728a890098
--
2.25.1
next reply other threads:[~2023-06-20 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 16:50 Isaku Yamahata [this message]
2023-06-20 16:50 ` [PATCH 1/3] exec/memory: Add symbolic value for memory listener priority for accel Isaku Yamahata
2023-06-20 16:50 ` [PATCH 2/3] exec/memory: Add symbol for memory listener priority for dev backend Isaku Yamahata
2023-06-20 16:50 ` [PATCH 3/3] exec/memory: Add symbol for the min value of memory listener priority Isaku Yamahata
2023-06-28 12:12 ` [PATCH 0/3] Add symbols for " Philippe Mathieu-Daudé
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=cover.1687279702.git.isaku.yamahata@intel.com \
--to=isaku.yamahata@intel.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).