From: Thomas Huth <thuth@redhat.com>
To: Zide Chen <zide.chen@intel.com>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, mst@redhat.com, cfontana@suse.de,
xiaoyao.li@intel.com, QEMU Trivial <qemu-trivial@nongnu.org>
Subject: Re: [PATCH 1/3] vl: Allow multiple -overcommit commands
Date: Tue, 21 May 2024 07:08:12 +0200 [thread overview]
Message-ID: <7b6bb859-acbe-4fb0-a8d5-c1698f597ef7@redhat.com> (raw)
In-Reply-To: <20240520174733.32979-2-zide.chen@intel.com>
On 20/05/2024 19.47, Zide Chen wrote:
> Both cpu-pm and mem-lock are related to system resource overcommit, but
> they are separate from each other, in terms of how they are realized,
> and of course, they are applied to different system resources.
>
> It's tempting to use separate command lines to specify their behavior.
> e.g., in the following example, the cpu-pm command is quietly
> overwritten, and it's not easy to notice it without careful inspection.
>
> --overcommit mem-lock=on
> --overcommit cpu-pm=on
>
> Fixes: c8c9dc42b7ca ("Remove the deprecated -realtime option")
> Signed-off-by: Zide Chen <zide.chen@intel.com>
> ---
> system/vl.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/system/vl.c b/system/vl.c
> index a3eede5fa5b8..ed682643805b 100644
> --- a/system/vl.c
> +++ b/system/vl.c
> @@ -3545,8 +3545,12 @@ void qemu_init(int argc, char **argv)
> if (!opts) {
> exit(1);
> }
> - enable_mlock = qemu_opt_get_bool(opts, "mem-lock", false);
> - enable_cpu_pm = qemu_opt_get_bool(opts, "cpu-pm", false);
> +
> + /* Don't override the -overcommit option if set */
> + enable_mlock = enable_mlock ||
> + qemu_opt_get_bool(opts, "mem-lock", false);
> + enable_cpu_pm = enable_cpu_pm ||
> + qemu_opt_get_bool(opts, "cpu-pm", false);
> break;
> case QEMU_OPTION_compat:
> {
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2024-05-21 5:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 17:47 [PATCH 0/3] improve -overcommit cpu-pm=on|off Zide Chen
2024-05-20 17:47 ` [PATCH 1/3] vl: Allow multiple -overcommit commands Zide Chen
2024-05-21 5:08 ` Thomas Huth [this message]
2024-05-21 5:16 ` Thomas Huth
2024-05-21 6:48 ` Chen, Zide
2024-05-21 6:54 ` Chen, Zide
2024-05-21 7:09 ` Chen, Zide
2024-05-20 17:47 ` [PATCH 2/3] target/i386: call cpu_exec_realizefn before x86_cpu_filter_features Zide Chen
2024-05-20 17:47 ` [PATCH 3/3] target/i386: Move host_cpu_enable_cpu_pm into kvm_cpu_realizefn() Zide Chen
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=7b6bb859-acbe-4fb0-a8d5-c1698f597ef7@redhat.com \
--to=thuth@redhat.com \
--cc=cfontana@suse.de \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=xiaoyao.li@intel.com \
--cc=zide.chen@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 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).