From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, qemu-devel@nongnu.org
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
kvm@vger.kernel.org, Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v6 0/2] kvm: limited x86 CPU power management
Date: Wed, 27 Jun 2018 17:08:26 +0200 [thread overview]
Message-ID: <fb0d7a20-a9cc-cbee-c3a3-daa244afd0d9@redhat.com> (raw)
In-Reply-To: <20180622192148.178309-1-mst@redhat.com>
On 22/06/2018 21:22, Michael S. Tsirkin wrote:
> This adds ability to expose some host CPU power management capabilities
> to guests. For intel guests, this is sufficient for guest to enable low
> power CPU states on idle. For AMD guests it isn't sufficient, deeper
> C-states are entered using System-IO.
>
> When enabled this puts CPU in a low power state with exit latencies that
> can go up to multiple milliseconds, and makes host scheduler as well as
> host utilities such as top and powertop think the CPU is constantly
> busy. Thus it has the effect of dedicating a host CPU for this guest.
>
> mwait based power management is tied closely to specifics of CPUID,
> making migration challenging. At this point only the non-migrateable
> -cpu host is supported.
>
> With this patch applied, VM latency is within the noise of
> baremetal for some benchmarks.
>
> perf bench sched pipe results:
> Before:
> 6.452 sec
> After:
> 4.382 sec
> Baremetal:
> 4.136 sec
>
> Changes since v5:
> Typo fix.
>
> Changes since v4:
> See v3, now for real.
>
> Changes since v3:
> At Paolo's suggestion, rename -dedicated to -overcommit.
>
> Changes since v2:
> At Daniel's suggestion, don't use the -realtime flag.
>
> At Paolo's suggestion, group this with memory lock flag
> which has a similar effect of dedicating memory to this VM.
>
> Michael S. Tsirkin (2):
> kvm: support -overcommit cpu-pm=on|off
> i386/cpu: make -cpu host support monitor/mwait
>
> include/sysemu/sysemu.h | 1 +
> target/i386/cpu.h | 9 +++++++++
> target/i386/cpu.c | 19 ++++++++++++++-----
> target/i386/kvm.c | 32 ++++++++++++++++++++++++++++++++
> vl.c | 32 +++++++++++++++++++++++++++++++-
> qemu-options.hx | 27 +++++++++++++++++++++++++--
> 6 files changed, 112 insertions(+), 8 deletions(-)
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2018-06-27 15:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 19:22 [Qemu-devel] [PATCH v6 0/2] kvm: limited x86 CPU power management Michael S. Tsirkin
2018-06-22 19:22 ` [Qemu-devel] [PATCH v6 2/2] i386/cpu: make -cpu host support monitor/mwait Michael S. Tsirkin
2018-06-22 19:22 ` [Qemu-devel] [PATCH v6 1/2] kvm: support -overcommit cpu-pm=on|off Michael S. Tsirkin
2018-06-25 9:40 ` Igor Mammedov
2018-06-26 14:06 ` Michael S. Tsirkin
2018-06-26 15:13 ` Igor Mammedov
2018-06-26 15:16 ` Michael S. Tsirkin
2018-06-27 13:42 ` Eduardo Habkost
2018-06-27 13:43 ` Eduardo Habkost
2018-06-22 21:55 ` [Qemu-devel] [PATCH v6 0/2] kvm: limited x86 CPU power management no-reply
2018-06-22 22:03 ` no-reply
2018-06-22 22:16 ` no-reply
2018-06-27 15:08 ` Paolo Bonzini [this message]
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=fb0d7a20-a9cc-cbee-c3a3-daa244afd0d9@redhat.com \
--to=pbonzini@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=mtosatti@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).