From: Eduardo Habkost <ehabkost@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Wanpeng Li" <kernellwp@gmail.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org,
"Radim Krčmář" <rkrcmar@redhat.com>
Subject: Re: [Qemu-devel] [PATCH RESEND v2] i386/kvm: add support for KVM_CAP_X86_DISABLE_EXITS
Date: Thu, 19 Apr 2018 18:53:20 -0300 [thread overview]
Message-ID: <20180419215320.GC29865@localhost.localdomain> (raw)
In-Reply-To: <98f48c44-e55a-2bd2-0d41-5643f35bce68@redhat.com>
On Thu, Apr 19, 2018 at 11:32:16PM +0200, Paolo Bonzini wrote:
> On 19/04/2018 21:56, Eduardo Habkost wrote:
> > On Thu, Apr 19, 2018 at 05:48:57PM +0200, Paolo Bonzini wrote:
> >> On 17/04/2018 22:59, Eduardo Habkost wrote:
> >>>> + if (disable_exits) {
> >>>> + disable_exits &= (KVM_X86_DISABLE_EXITS_MWAIT |
> >>>> + KVM_X86_DISABLE_EXITS_HLT |
> >>>> + KVM_X86_DISABLE_EXITS_PAUSE);
> >>>> + if (env->user_features[FEAT_KVM] & KVM_PV_UNHALT) {
> >>>> + disable_exits &= ~KVM_X86_DISABLE_EXITS_HLT;
> >>>> + }
> >>>
> >>> In the future, if we decide to enable kvm-pv-unhalt by default,
> >>> should "-cpu ...,kvm-hint-dedicated=on" disable kvm-pv-unhalt
> >>> automatically, or should we require an explicit
> >>> "kvm-hint-dedicated=on,kvm-pv-unhalt=off" option?
> >>
> >> It should be automatic.
> >>
> >>> For today's defaults, this patch solves the problem, only one
> >>> thing is missing before I give my R-b: we need to clearly
> >>> document what exactly are the consequences and requirements of
> >>> setting kvm-hint-dedicated=on (I'm not sure if the best place for
> >>> this is qemu-options.hx, x86_cpu_list(), or somewhere else).
> >>
> >> I don't think we have a good place for this kind of documentation,
> >> unfortunately. Right now it is mentioned in
> >> Documentation/virtual/kvm/cpuid.txt.
> >
> > With this patch, the QEMU option will do more than just setting
> > the CPUID bit, that's why I miss more detailed documentation on
> > the QEMU side. But I agree we have no obvious place for that
> > documentation.
> >
> > In the worst case we can just add a code comment on top of
> > feature_word_info[FEAT_KVM_HINTS].feat_names warning that
> > kvm-hint-dedicated won't just enable the flag on CPUID and has
> > other side-effects.
>
> Maybe we should use "-realtime dedicated=on" instead of, or in addition
> to kvm-hint-dedicated=on?
Maybe it's a better idea than overloading an option that is only
expected to control a CPUID bit.
--
Eduardo
next prev parent reply other threads:[~2018-04-19 21:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 8:24 [Qemu-devel] [PATCH RESEND v2] i386/kvm: add support for KVM_CAP_X86_DISABLE_EXITS Wanpeng Li
2018-04-17 8:28 ` no-reply
2018-04-17 18:08 ` Michael S. Tsirkin
2018-04-18 1:09 ` Wanpeng Li
2018-05-11 21:57 ` Michael S. Tsirkin
2018-05-12 0:49 ` Wanpeng Li
2018-04-17 20:59 ` Eduardo Habkost
2018-04-18 1:20 ` Wanpeng Li
2018-04-19 15:48 ` Paolo Bonzini
2018-04-19 19:56 ` Eduardo Habkost
2018-04-19 21:32 ` Paolo Bonzini
2018-04-19 21:53 ` Eduardo Habkost [this message]
2018-05-11 22:12 ` Michael S. Tsirkin
2018-05-16 12:34 ` Eduardo Habkost
2018-05-16 14:26 ` Michael S. Tsirkin
2018-05-17 17:34 ` Eduardo Habkost
2018-05-17 17:57 ` Michael S. Tsirkin
2018-05-17 18:18 ` Eduardo Habkost
2018-05-16 12:44 ` Paolo Bonzini
2018-05-16 14:22 ` Michael S. Tsirkin
2018-05-16 15:04 ` Paolo Bonzini
2018-05-16 15:13 ` Michael S. Tsirkin
2018-05-16 15:33 ` Eduardo Habkost
2018-05-16 16:21 ` Michael S. Tsirkin
2018-05-16 17:20 ` Eduardo Habkost
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=20180419215320.GC29865@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkrcmar@redhat.com \
/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).