From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>, Tao Xu <tao3.xu@intel.com>
Cc: rkrcmar@redhat.com, corbet@lwn.net, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, hpa@zytor.com,
sean.j.christopherson@intel.com, x86@kernel.org,
kvm@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, jingqi.liu@intel.com
Subject: Re: [PATCH v2 1/3] KVM: x86: add support for user wait instructions
Date: Wed, 29 May 2019 03:25:39 +0200 [thread overview]
Message-ID: <bcf669c8-81f4-0024-5f66-c40c6d519c62@redhat.com> (raw)
In-Reply-To: <20190527103003.GX2623@hirez.programming.kicks-ass.net>
On 27/05/19 12:30, Peter Zijlstra wrote:
>> This patch adds support for UMONITOR, UMWAIT and TPAUSE instructions
>> in kvm, and by default dont't expose it to kvm and provide a capability
>> to enable it.
>
> I'm thinking this should be conditional on the guest being a 1:1 guest,
> and I also seem to remember we have bits for that already -- they were
> used to disable paravirt spinlocks for example.
This should be userspace's choice. It would indeed be silly to enable
this while overcommitted, but KVM doesn't really care.
Paolo
next prev parent reply other threads:[~2019-05-29 1:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 7:56 [PATCH v2 0/3] KVM: x86: Enable user wait instructions Tao Xu
2019-05-24 7:56 ` [PATCH v2 1/3] KVM: x86: add support for " Tao Xu
2019-05-27 10:30 ` Peter Zijlstra
2019-05-28 5:11 ` Tao Xu
2019-05-28 6:11 ` Wanpeng Li
2019-05-28 7:19 ` Tao Xu
2019-05-29 1:26 ` Paolo Bonzini
2019-05-29 1:25 ` Paolo Bonzini [this message]
2019-05-29 1:24 ` Paolo Bonzini
2019-05-29 2:05 ` Tao Xu
2019-05-29 2:38 ` Paolo Bonzini
2019-05-29 3:12 ` Tao Xu
2019-05-24 7:56 ` [PATCH v2 2/3] KVM: vmx: Emulate MSR IA32_UMWAIT_CONTROL Tao Xu
2019-05-29 1:29 ` Paolo Bonzini
2019-05-29 1:38 ` Tao Xu
2019-05-24 7:56 ` [PATCH v2 3/3] KVM: vmx: handle vm-exit for UMWAIT and TPAUSE Tao Xu
2019-05-29 1:28 ` Paolo Bonzini
2019-05-29 2:25 ` Tao Xu
2019-05-29 2:39 ` 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=bcf669c8-81f4-0024-5f66-c40c6d519c62@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=hpa@zytor.com \
--cc=jingqi.liu@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rkrcmar@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=tao3.xu@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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