From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Isaku Yamahata <isaku.yamahata@intel.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH 0/3] Add symbols for memory listener priority
Date: Wed, 28 Jun 2023 14:12:02 +0200 [thread overview]
Message-ID: <4c1044c1-eec7-9396-b33e-14b450e2837e@linaro.org> (raw)
In-Reply-To: <cover.1687279702.git.isaku.yamahata@intel.com>
On 20/6/23 18:50, Isaku Yamahata wrote:
> 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
Series:
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
and queued fixing the typos, thanks.
prev parent reply other threads:[~2023-06-28 12:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 16:50 [PATCH 0/3] Add symbols for memory listener priority Isaku Yamahata
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 ` Philippe Mathieu-Daudé [this message]
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=4c1044c1-eec7-9396-b33e-14b450e2837e@linaro.org \
--to=philmd@linaro.org \
--cc=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).