From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
kvm@vger.kernel.org, "Marcelo Tosatti" <mtosatti@redhat.com>,
qemu-devel@nongnu.org, "Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v2 0/2] kvm: x86 CPU power management
Date: Fri, 15 Jun 2018 16:52:28 +0300 [thread overview]
Message-ID: <20180615164645-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <2219a7fd-b496-6653-b79a-c20136727f98@redhat.com>
On Thu, Jun 14, 2018 at 05:40:41PM +0200, Paolo Bonzini wrote:
> On 14/06/2018 10:18, Daniel P. Berrangé wrote:
> > I don't think
> > the -realtime flag should ever have been introduced, and we certainly
> > shouldn't add more stuff under it.
> >
> > "-realtime" is referring to a very specific use case, while the
> > properties listed under it are all general purpose features. Real
> > time guests just happen to be one possible use case, but it is
> > valid to use them for non-real time guests.
> >
> > IOW, I think we should just have this as an option under -cpu or
> > some other *functionally* named option, not a option named after
> > a specific usage scenario.
>
> "-cpu" is certainly wrong for KVM_CAP_X86_DISABLE_EXITS. "-cpu" is a
> device option, while this is about host behavior. "-realtime"'s name is
> awful, but I still think it's the best place for this option. Maybe we
> could call it "-realtime power-mgmt={host|guest}".
I don't feel it's a good name. The new flag allows guest to put CPU
into a low power state without host knowing about it. This will affect
other guests on the same host CPU. It doesn't however limit power
management to guest only, things like speedstep remain under host
control.
> A separate issue is whether the same flag should control both
> KVM_CAP_X86_DISABLE_EXITS and the monitor/mwait CPUID leaf. Eduardo,
> what do you think?
>
> Paolo
It's just for -cpu host.
next prev parent reply other threads:[~2018-06-15 13:52 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
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 [this message]
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=20180615164645-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
--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).