aboutsummaryrefslogtreecommitdiff
path: root/target/i386/kvm
diff options
context:
space:
mode:
authorZide Chen <zide.chen@intel.com>2024-06-03 17:02:21 -0700
committerMichael Tokarev <mjt@tls.msk.ru>2024-06-30 19:51:44 +0300
commit3fd73736c69b71035cf1154ef58e8fa494f8612c (patch)
treee03c77c4ea71c9ada1f99ee9b68a26f4d46c5898 /target/i386/kvm
parent2b5d12b68514e3d81086a65fc8496822d5bd4359 (diff)
downloadqemu-3fd73736c69b71035cf1154ef58e8fa494f8612c.zip
qemu-3fd73736c69b71035cf1154ef58e8fa494f8612c.tar.gz
qemu-3fd73736c69b71035cf1154ef58e8fa494f8612c.tar.bz2
vl: Allow multiple -overcommit commands
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> Reviewed-by: Michael Tokarev <mjt@tls.msk.ru> Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
Diffstat (limited to 'target/i386/kvm')
0 files changed, 0 insertions, 0 deletions