From: Igor Mammedov <imammedo@redhat.com>
To: Zide Chen <zide.chen@intel.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com, mst@redhat.com,
thuth@redhat.com, cfontana@suse.de, xiaoyao.li@intel.com,
qemu-trivial@nongnu.org, seanjc@google.com, zhao1.liu@intel.com
Subject: Re: [PATCH V3 1/2] vl: Allow multiple -overcommit commands
Date: Wed, 5 Jun 2024 15:34:51 +0200 [thread overview]
Message-ID: <20240605153451.5c234180@imammedo.users.ipa.redhat.com> (raw)
In-Reply-To: <20240604000222.75065-2-zide.chen@intel.com>
On Mon, 3 Jun 2024 17:02:21 -0700
Zide Chen <zide.chen@intel.com> 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")
> Suggested-by: Thomas Huth <thuth@redhat.com>
> Signed-off-by: Zide Chen <zide.chen@intel.com>
> Reviewed-by: Thomas Huth <thuth@redhat.com>
> Reviewed-by: Zhao Liu <zhao1.liu@intel.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
> ---
>
> V3: added Reviewed-by
>
> v2:
> Thanks to Thomas' suggestion, changed to this better approach, which
> is more generic and can handle situations like: "enabled the option in
> the config file, and now you'd like to disable it on the command line
> again".
>
> system/vl.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/system/vl.c b/system/vl.c
> index a3eede5fa5b8..dfa6cdd9283b 100644
> --- a/system/vl.c
> +++ b/system/vl.c
> @@ -3545,8 +3545,8 @@ 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);
> + enable_mlock = qemu_opt_get_bool(opts, "mem-lock", enable_mlock);
> + enable_cpu_pm = qemu_opt_get_bool(opts, "cpu-pm", enable_cpu_pm);
> break;
> case QEMU_OPTION_compat:
> {
next prev parent reply other threads:[~2024-06-05 13:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 0:02 [PATCH V3 0/2] improve -overcommit cpu-pm=on|off Zide Chen
2024-06-04 0:02 ` [PATCH V3 1/2] vl: Allow multiple -overcommit commands Zide Chen
2024-06-05 13:34 ` Igor Mammedov [this message]
2024-06-04 0:02 ` [PATCH V3 2/2] target/i386: Advertise MWAIT iff host supports Zide Chen
2024-06-04 4:02 ` Zhao Liu
2024-06-04 15:08 ` Xiaoyao Li
2024-06-05 13:41 ` Igor Mammedov
2024-06-05 13:49 ` [PATCH V3 0/2] improve -overcommit cpu-pm=on|off Igor Mammedov
2024-06-05 18:33 ` Chen, Zide
2024-06-17 12:47 ` Michael Tokarev
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=20240605153451.5c234180@imammedo.users.ipa.redhat.com \
--to=imammedo@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=seanjc@google.com \
--cc=thuth@redhat.com \
--cc=xiaoyao.li@intel.com \
--cc=zhao1.liu@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).