Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757647Ab2EOL0S (ORCPT ); Tue, 15 May 2012 07:26:18 -0400 Received: from nat28.tlf.novell.com ([130.57.49.28]:56411 "EHLO nat28.tlf.novell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757095Ab2EOL0O convert rfc822-to-8bit (ORCPT ); Tue, 15 May 2012 07:26:14 -0400 Message-Id: <4FB2598D0200007800083C55@nat28.tlf.novell.com> X-Mailer: Novell GroupWise Internet Agent 12.0.0 Date: Tue, 15 May 2012 12:26:37 +0100 From: "Jan Beulich" To: "Ingo Molnar" Cc: "Stephan Diestelhorst" , "Peter Zijlstra" , "Attilio Rao" , "Stefano Stabellini" , "Andi Kleen" , "Jeremy Fitzhardinge" , "X86" , "Thomas Gleixner" , "Andrew Morton" , "Linus Torvalds" , "Raghavendra K T" , "Srivatsa Vaddagiri" , "Virtualization" , "Xen Devel" , "Konrad Rzeszutek Wilk" , "Avi Kivity" , "Gleb Natapov" , "Ingo Molnar" , "Marcelo Tosatti" , "Greg Kroah-Hartman" , "KVM" , , "LKML" , "H. Peter Anvin" Subject: Re: [Xen-devel] [PATCH RFC V8 0/17] Paravirtualized ticket spinlocks References: <4FA7BABA.4040700@redhat.com> <4FA7CC05.50808@linux.vnet.ibm.com> <4FA7CCA2.4030408@redhat.com> <4FA7D06B.60005@linux.vnet.ibm.com> <20120507134611.GB5533@linux.vnet.ibm.com> <4FA7D2E5.1020607@redhat.com> <4FA7D3F7.9080005@linux.vnet.ibm.com> <4FA7D50D.1020209@redhat.com> <4FA7E06E.20304@linux.vnet.ibm.com> <4FA7E1C8.7010509@redhat.com> <20120507172527.GA5357@gmail.com> In-Reply-To: <20120507172527.GA5357@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8BIT Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 871 Lines: 25 >>> On 07.05.12 at 19:25, Ingo Molnar wrote: (apologies for the late reply, the mail just now made it to my inbox via xen-devel) > I'll hold off on the whole thing - frankly, we don't want this > kind of Xen-only complexity. If KVM can make use of PLE then Xen > ought to be able to do it as well. It does - for fully virtualized guests. For para-virtualized ones, it can't (as the hardware feature is an extension to VMX/SVM). > If both Xen and KVM makes good use of it then that's a different > matter. I saw in a later reply that you're now tending towards trying it out at least - thanks. Jan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/