From: Eduardo Habkost <ehabkost@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v2 1/2] kvm: support -realtime cpu-pm=on|off
Date: Wed, 13 Jun 2018 18:00:22 -0300 [thread overview]
Message-ID: <20180613210022.GG24764@localhost.localdomain> (raw)
In-Reply-To: <20180612184616.90838-2-mst@redhat.com>
On Tue, Jun 12, 2018 at 09:47:11PM +0300, Michael S. Tsirkin wrote:
> With this flag, kvm allows guest to control host CPU power state. This
> increases latency for other processes using same host CPU in an
> unpredictable way, but if decreases idle entry/exit times for the
> running VCPU.
>
> Follow-up patches will expose this capability to guest
> (using mwait leaf).
>
> Based on a patch by Wanpeng Li <kernellwp@gmail.com> .
>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
> include/sysemu/sysemu.h | 1 +
> target/i386/kvm.c | 22 ++++++++++++++++++++++
> vl.c | 6 ++++++
> qemu-options.hx | 9 +++++++--
> 4 files changed, 36 insertions(+), 2 deletions(-)
>
> diff --git a/include/sysemu/sysemu.h b/include/sysemu/sysemu.h
> index e893f72f3b..b921c6f3b7 100644
> --- a/include/sysemu/sysemu.h
> +++ b/include/sysemu/sysemu.h
> @@ -128,6 +128,7 @@ extern bool boot_strict;
> extern uint8_t *boot_splash_filedata;
> extern size_t boot_splash_filedata_size;
> extern bool enable_mlock;
> +extern bool enable_cpu_pm;
After looking at patch 2/2, I see that the global variable is
useful, and it's consistent with the existing enable_mlock
variable.
> extern uint8_t qemu_extra_params_fw[2];
> extern QEMUClockType rtc_clock;
> extern const char *mem_path;
> diff --git a/target/i386/kvm.c b/target/i386/kvm.c
> index 44f70733e7..f093d55209 100644
> --- a/target/i386/kvm.c
> +++ b/target/i386/kvm.c
> @@ -1357,6 +1357,28 @@ int kvm_arch_init(MachineState *ms, KVMState *s)
> smram_machine_done.notify = register_smram_listener;
> qemu_add_machine_init_done_notifier(&smram_machine_done);
> }
> +
> + if (enable_cpu_pm) {
> + int disable_exits = kvm_check_extension(s, KVM_CAP_X86_DISABLE_EXITS);
> + int ret;
> +
> +/* Work around for kernel header with a typo. TODO: fix header and drop. */
> +#if defined(KVM_X86_DISABLE_EXITS_HTL) && !defined(KVM_X86_DISABLE_EXITS_HLT)
> +#define KVM_X86_DISABLE_EXITS_HLT KVM_X86_DISABLE_EXITS_HTL
> +#endif
> + if (disable_exits) {
> + disable_exits &= (KVM_X86_DISABLE_EXITS_MWAIT |
> + KVM_X86_DISABLE_EXITS_HLT |
> + KVM_X86_DISABLE_EXITS_PAUSE);
> + }
> +
> + ret = kvm_vm_enable_cap(s, KVM_CAP_X86_DISABLE_EXITS, 0,
> + disable_exits);
Isn't the kvm_vm_enable_cap() call supposed to be inside the "if
(disable_exits)" block?
> + if (ret < 0) {
> + error_report("kvm: guest stopping CPU not supported: %s", strerror(-ret));
> + }
> + }
> +
> return 0;
> }
[...]
--
Eduardo
next prev parent reply other threads:[~2018-06-13 21:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 18:47 [Qemu-devel] [PATCH v2 0/2] kvm: x86 CPU power management Michael S. Tsirkin
2018-06-12 18:47 ` [Qemu-devel] [PATCH v2 1/2] kvm: support -realtime cpu-pm=on|off Michael S. Tsirkin
2018-06-13 20:35 ` Eduardo Habkost
2018-06-13 21:00 ` Eduardo Habkost [this message]
2018-06-13 21:53 ` Michael S. Tsirkin
2018-06-12 18:47 ` [Qemu-devel] [PATCH v2 2/2] i386/cpu: make -cpu host support monitor/mwait Michael S. Tsirkin
2018-06-13 21:24 ` Eduardo Habkost
2018-06-12 19:18 ` [Qemu-devel] [PATCH v2 0/2] kvm: x86 CPU power management no-reply
2018-06-12 20:29 ` Michael S. Tsirkin
2018-06-13 22:34 ` Marcelo Tosatti
2018-06-13 23:37 ` Michael S. Tsirkin
2018-06-15 18:32 ` Marcelo Tosatti
2018-06-15 21:53 ` Michael S. Tsirkin
2018-06-14 8:18 ` Daniel P. Berrangé
2018-06-14 15:40 ` Paolo Bonzini
2018-06-14 15:44 ` Daniel P. Berrangé
2018-06-14 20:32 ` Paolo Bonzini
2018-06-15 14:15 ` Michael S. Tsirkin
2018-06-14 16:53 ` Eduardo Habkost
2018-06-14 21:21 ` Paolo Bonzini
2018-06-15 13:52 ` Michael S. Tsirkin
2018-06-22 13:06 ` Kashyap Chamarthy
2018-06-22 19:18 ` Michael S. Tsirkin
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=20180613210022.GG24764@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).