From: Paolo Bonzini <pbonzini@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>,
Waiman Long <Waiman.Long@hp.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Arnd Bergmann <arnd@arndb.de>,
Peter Zijlstra <peterz@infradead.org>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>,
kvm@vger.kernel.org, Aswin Chandramouleeswaran <aswin@hp.com>,
Andi Kleen <andi@firstfloor.org>,
Michel Lespinasse <walken@google.com>,
Alok Kataria <akataria@vmware.com>,
linux-arch@vger.kernel.org, Gleb Natapov <gleb@redhat.com>,
x86@kernel.org, xen-devel@lists.xenproject.org,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Scott J Norton <scott.norton@hp.com>,
Steven Rostedt <rostedt@goodmis.org>,
Chris Wright <chrisw@sous-sol.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
virtualization@lists.linux-foundation.org,
Chegu Vinod <chegu_vinod@hp.com>, Oleg Nesterov <oleg@redhat.com>,
linux-kernel@vger.kernel.org,
David Vrabel <david.vrabel@citrix.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v7 06/11] pvqspinlock, x86: Allow unfair queue spinlock in a KVM guest
Date: Thu, 20 Mar 2014 23:40:08 +0100 [thread overview]
Message-ID: <532B6E48.2070205@redhat.com> (raw)
In-Reply-To: <532B6BC8.8010502@zytor.com>
Il 20/03/2014 23:29, H. Peter Anvin ha scritto:
> > No! Please do what I asked you to do. You are not handling Hyper-V or
> > VMWare. Just use X86_FEATURE_HYPERVISOR and it will cover all
> > hypervisors that actually follow Intel's guidelines.
>
> And for those that don't, we should turn on X86_FEATURE_HYPERVISOR in
> the Linux enumeration code as we do for other features we detect
> independently.
Yeah, but all the hypervisors we detect right now are fine. Not
surprising, since Microsoft won't certify Windows on your hypervisor
unless you set the bit, and KVM/Xen/VMware are all certified (Hyper-V
does not go through the same certification, but sets it anyway).
I got a second-hand report that VirtualBox doesn't set it---and I
haven't verified that yet---but we don't even try to detect vbox right now.
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>,
Waiman Long <Waiman.Long@hp.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Arnd Bergmann <arnd@arndb.de>,
Peter Zijlstra <peterz@infradead.org>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>,
Gleb Natapov <gleb@redhat.com>,
Aswin Chandramouleeswaran <aswin@hp.com>,
Andi Kleen <andi@firstfloor.org>,
Michel Lespinasse <walken@google.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
linux-arch@vger.kernel.org, kvm@vger.kernel.org, x86@kernel.org,
xen-devel@lists.xenproject.org,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Scott J Norton <scott.norton@hp.com>,
Steven Rostedt <rostedt@goodmis.org>,
Chris Wright <chrisw@sous-sol.org>,
Alok Kataria <akataria@vmware.com>,
virtualization@lists.linux-foundation.org,
Chegu Vinod <chegu_vinod@hp.com>, Oleg Nesterov <oleg@redhat.com>,
linux-kernel@vger.kernel.org,
David Vrabel <david.vrabel@citrix.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v7 06/11] pvqspinlock, x86: Allow unfair queue spinlock in a KVM guest
Date: Thu, 20 Mar 2014 23:40:08 +0100 [thread overview]
Message-ID: <532B6E48.2070205@redhat.com> (raw)
Message-ID: <20140320224008.SKOr-cPajT3krJi_8W7C19zaMM3bm2CgQ1ys32NYuKI@z> (raw)
In-Reply-To: <532B6BC8.8010502@zytor.com>
Il 20/03/2014 23:29, H. Peter Anvin ha scritto:
> > No! Please do what I asked you to do. You are not handling Hyper-V or
> > VMWare. Just use X86_FEATURE_HYPERVISOR and it will cover all
> > hypervisors that actually follow Intel's guidelines.
>
> And for those that don't, we should turn on X86_FEATURE_HYPERVISOR in
> the Linux enumeration code as we do for other features we detect
> independently.
Yeah, but all the hypervisors we detect right now are fine. Not
surprising, since Microsoft won't certify Windows on your hypervisor
unless you set the bit, and KVM/Xen/VMware are all certified (Hyper-V
does not go through the same certification, but sets it anyway).
I got a second-hand report that VirtualBox doesn't set it---and I
haven't verified that yet---but we don't even try to detect vbox right now.
Paolo
next prev parent reply other threads:[~2014-03-20 22:40 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 20:13 [PATCH v7 00/11] qspinlock: a 4-byte queue spinlock with PV support Waiman Long
2014-03-19 20:13 ` [PATCH v7 01/11] qspinlock: A generic 4-byte queue spinlock implementation Waiman Long
2014-03-19 20:13 ` Waiman Long
2014-03-19 20:14 ` [PATCH v7 02/11] qspinlock, x86: Enable x86-64 to use queue spinlock Waiman Long
2014-03-19 20:14 ` Waiman Long
2014-03-19 20:24 ` Konrad Rzeszutek Wilk
2014-03-19 20:24 ` Konrad Rzeszutek Wilk
2014-03-21 3:36 ` Waiman Long
2014-03-21 3:36 ` Waiman Long
2014-03-21 3:36 ` Waiman Long
2014-03-19 20:24 ` Konrad Rzeszutek Wilk
2014-03-19 20:14 ` [PATCH v7 03/11] qspinlock: More optimized code for smaller NR_CPUS Waiman Long
2014-03-19 20:14 ` Waiman Long
2014-03-19 20:14 ` [PATCH v7 04/11] qspinlock: Optimized code path for 2 contending tasks Waiman Long
2014-03-19 20:14 ` Waiman Long
2014-03-19 20:14 ` [PATCH v7 05/11] pvqspinlock, x86: Allow unfair spinlock in a PV guest Waiman Long
2014-03-19 20:14 ` Waiman Long
2014-03-19 20:14 ` [PATCH v7 06/11] pvqspinlock, x86: Allow unfair queue spinlock in a KVM guest Waiman Long
2014-03-19 20:14 ` Waiman Long
2014-03-20 22:01 ` Paolo Bonzini
2014-03-20 22:01 ` Paolo Bonzini
2014-03-20 22:29 ` H. Peter Anvin
2014-03-20 22:29 ` H. Peter Anvin
2014-03-20 22:40 ` Paolo Bonzini
2014-03-20 22:40 ` Paolo Bonzini [this message]
2014-03-20 22:40 ` Paolo Bonzini
2014-03-20 22:29 ` H. Peter Anvin
2014-03-21 21:27 ` Waiman Long
2014-03-21 21:27 ` Waiman Long
2014-03-20 22:01 ` Paolo Bonzini
2014-03-19 20:14 ` [PATCH v7 07/11] pvqspinlock, x86: Allow unfair queue spinlock in a XEN guest Waiman Long
2014-03-19 20:28 ` Konrad Rzeszutek Wilk
2014-03-19 20:28 ` Konrad Rzeszutek Wilk
2014-03-19 20:28 ` Konrad Rzeszutek Wilk
2014-03-21 3:40 ` Waiman Long
2014-03-21 3:40 ` Waiman Long
2014-03-21 3:40 ` Waiman Long
2014-03-19 20:14 ` Waiman Long
2014-03-19 20:14 ` [PATCH v7 08/11] pvqspinlock, x86: Rename paravirt_ticketlocks_enabled Waiman Long
2014-03-19 20:14 ` Waiman Long
2014-03-19 20:14 ` [PATCH v7 09/11] pvqspinlock, x86: Add qspinlock para-virtualization support Waiman Long
2014-03-19 20:14 ` Waiman Long
2014-03-19 20:14 ` [PATCH v7 10/11] pvqspinlock, x86: Enable qspinlock PV support for KVM Waiman Long
2014-03-20 22:07 ` Paolo Bonzini
2014-03-20 22:07 ` Paolo Bonzini
2014-03-21 21:41 ` Waiman Long
2014-03-21 21:41 ` Waiman Long
2014-03-20 22:07 ` Paolo Bonzini
2014-03-19 20:14 ` Waiman Long
2014-03-19 20:14 ` [PATCH RFC v7 11/11] pvqspinlock, x86: Enable qspinlock PV support for XEN Waiman Long
2014-03-19 20:14 ` Waiman Long
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=532B6E48.2070205@redhat.com \
--to=pbonzini@redhat.com \
--cc=Waiman.Long@hp.com \
--cc=akataria@vmware.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=arnd@arndb.de \
--cc=aswin@hp.com \
--cc=boris.ostrovsky@oracle.com \
--cc=chegu_vinod@hp.com \
--cc=chrisw@sous-sol.org \
--cc=david.vrabel@citrix.com \
--cc=gleb@redhat.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=kvm@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=raghavendra.kt@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=scott.norton@hp.com \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.org \
--cc=walken@google.com \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.