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 v6 1/2] kvm: support -overcommit cpu-pm=on|off
Date: Wed, 27 Jun 2018 10:43:35 -0300 [thread overview]
Message-ID: <20180627134335.GC914@localhost.localdomain> (raw)
In-Reply-To: <20180622192148.178309-2-mst@redhat.com>
On Fri, Jun 22, 2018 at 10:22:05PM +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, so to use it QEMU needs a hint about whether host CPU is
> overcommitted, hence the flag name.
>
> 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>
Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>
--
Eduardo
next prev parent reply other threads:[~2018-06-27 13:43 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 [this message]
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
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=20180627134335.GC914@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).