From: Wanpeng Li <kernellwp@gmail.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
kvm <kvm@vger.kernel.org>, "Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>
Subject: Re: [Qemu-devel] [PATCH RESEND v2] i386/kvm: add support for KVM_CAP_X86_DISABLE_EXITS
Date: Wed, 18 Apr 2018 09:20:29 +0800 [thread overview]
Message-ID: <CANRm+CwWpVympddFxMjzjVytcEdKwTo=cxA0YzeceE36J4eomw@mail.gmail.com> (raw)
In-Reply-To: <20180417205913.GC29865@localhost.localdomain>
2018-04-18 4:59 GMT+08:00 Eduardo Habkost <ehabkost@redhat.com>:
> On Tue, Apr 17, 2018 at 01:24:15AM -0700, Wanpeng Li wrote:
[.../...]
>>
>> + if (env->features[FEAT_KVM_HINTS] & KVM_HINTS_DEDICATED) {
>> + int disable_exits = kvm_check_extension(cs->kvm_state, KVM_CAP_X86_DISABLE_EXITS);
>> +
>> + 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?
>
> 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).
What's your opinion, Paolo?
Regards,
Wanpeng Li
next prev parent reply other threads:[~2018-04-18 1:20 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 [this message]
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
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='CANRm+CwWpVympddFxMjzjVytcEdKwTo=cxA0YzeceE36J4eomw@mail.gmail.com' \
--to=kernellwp@gmail.com \
--cc=ehabkost@redhat.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).