linux-kernel - Re: [PATCH v7 06/11] pvqspinlock, x86: Allow unfair queue spinlock in a KVM guest

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <532B6E48.2070205@redhat.com>
Date:	Thu, 20 Mar 2014 23:40:08 +0100
From:	Paolo Bonzini <pbonzini@...hat.com>
To:	"H. Peter Anvin" <hpa@...or.com>, Waiman Long <Waiman.Long@...com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>, Arnd Bergmann <arnd@...db.de>,
	Peter Zijlstra <peterz@...radead.org>
CC:	Jeremy Fitzhardinge <jeremy@...p.org>,
	Raghavendra K T <raghavendra.kt@...ux.vnet.ibm.com>,
	Gleb Natapov <gleb@...hat.com>,
	Aswin Chandramouleeswaran <aswin@...com>,
	Andi Kleen <andi@...stfloor.org>,
	Michel Lespinasse <walken@...gle.com>,
	Boris Ostrovsky <boris.ostrovsky@...cle.com>,
	linux-arch@...r.kernel.org, kvm@...r.kernel.org, x86@...nel.org,
	xen-devel@...ts.xenproject.org,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Scott J Norton <scott.norton@...com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Chris Wright <chrisw@...s-sol.org>,
	Alok Kataria <akataria@...are.com>,
	virtualization@...ts.linux-foundation.org,
	Chegu Vinod <chegu_vinod@...com>,
	Oleg Nesterov <oleg@...hat.com>, linux-kernel@...r.kernel.org,
	David Vrabel <david.vrabel@...rix.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH v7 06/11] pvqspinlock, x86: Allow unfair queue spinlock
 in a KVM guest

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/