From: "Chen, Zide" <zide.chen@intel.com>
To: Thomas Huth <thuth@redhat.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: Mon, 20 May 2024 23:48:29 -0700 [thread overview]
Message-ID: <06c28d67-5b82-416c-ae6f-a8c56f63d0fa@intel.com> (raw)
In-Reply-To: <342858a6-c8bd-45fe-8b91-8e0a444eb2e6@redhat.com>
On 5/20/2024 10:16 PM, Thomas Huth wrote:
> On 21/05/2024 07.08, Thomas Huth wrote:
>> 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>
>
> Ah, wait, actually, this is a bad idea, too, since now you cannot
> disable an enabled option anymore. Imagine that you have for example
> enabled the option in the config file, and now you'd like to disable it
> on the command line again - you're stuck with the enabled setting in
> that case.
>
> I think the better solution is to replace the "false" default value at
> the end:
>
> enable_mlock = qemu_opt_get_bool(opts, "mem-lock", enable_mlock);
> enable_cpu_pm = qemu_opt_get_bool(opts, "cpu-pm", enable_cpu_pm);
>
> What do you think about this?
Thank you very much! This is a very good idea, and I can update it in V2.
>
> Thomas
>
next prev parent reply other threads:[~2024-05-21 6:49 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
2024-05-21 5:16 ` Thomas Huth
2024-05-21 6:48 ` Chen, Zide [this message]
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=06c28d67-5b82-416c-ae6f-a8c56f63d0fa@intel.com \
--to=zide.chen@intel.com \
--cc=cfontana@suse.de \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=thuth@redhat.com \
--cc=xiaoyao.li@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).