From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755185Ab1J0KRz (ORCPT ); Thu, 27 Oct 2011 06:17:55 -0400 Received: from mx1.redhat.com ([209.132.183.28]:16762 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753835Ab1J0KRx (ORCPT ); Thu, 27 Oct 2011 06:17:53 -0400 Message-ID: <4EA92FAB.1050607@redhat.com> Date: Thu, 27 Oct 2011 12:17:15 +0200 From: Avi Kivity User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110930 Thunderbird/7.0.1 MIME-Version: 1.0 To: Raghavendra K T CC: Srivatsa Vaddagiri , Raghavendra K T , Greg Kroah-Hartman , "H. Peter Anvin" , Gleb Natapov , Virtualization , Jeremy Fitzhardinge , x86@kernel.org, KVM , Dave Jiang , Thomas Gleixner , Stefano Stabellini , Xen , Sedat Dilek , Yinghai Lu , Marcelo Tosatti , Ingo Molnar , Rik van Riel , Konrad Rzeszutek Wilk , LKML , Suzuki Poulose , Peter Zijlstra , Ryan Harper Subject: Re: [PATCH RFC V2 3/5] kvm hypervisor : Add two hypercalls to support pv-ticketlock References: <20111023190307.16364.35381.sendpatchset@oc5400248562.ibm.com> <20111023190558.16364.2136.sendpatchset@oc5400248562.ibm.com> <4EA53A7D.300@redhat.com> <20111024122734.GA10634@linux.vnet.ibm.com> <4EA56385.9040302@redhat.com> <20111024135032.GB10634@linux.vnet.ibm.com> <4EA6FEC2.1060209@linux.vnet.ibm.com> <4EA7E21B.8020805@redhat.com> <4EA85A9D.5060203@linux.vnet.ibm.com> In-Reply-To: <4EA85A9D.5060203@linux.vnet.ibm.com> X-Enigmail-Version: 1.3.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/26/2011 09:08 PM, Raghavendra K T wrote: > On 10/26/2011 04:04 PM, Avi Kivity wrote: >> On 10/25/2011 08:24 PM, Raghavendra K T wrote: > CCing Ryan also >>> >>> So then do also you foresee the need for directed yield at some point, >>> to address LHP? provided we have good improvements to prove. >> >> Doesn't this patchset completely eliminate lock holder preemption? >> > Basically I was curious whether we can do more better with your > directed yield discussions in https://lkml.org/lkml/2010/8/2/106 . > > I felt we can get little more improvement with doing directed yield to > lock-holder in case of LHP than sleeping. But I may be wrong. > > So wanted to get the feedback, on whether I am thinking in right > direction. i guess donating some time to the lock holder could help, but not by much. The problem with non-pv spinlocks is that you can't just sleep, since no one will wake you up, so you have to actively boost the lock holder. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.