From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934040Ab1LGQcE (ORCPT ); Wed, 7 Dec 2011 11:32:04 -0500 Received: from e28smtp09.in.ibm.com ([122.248.162.9]:42093 "EHLO e28smtp09.in.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756574Ab1LGQcA (ORCPT ); Wed, 7 Dec 2011 11:32:00 -0500 Message-ID: <4EDF94F0.2080201@linux.vnet.ibm.com> Date: Wed, 07 Dec 2011 22:01:44 +0530 From: Raghavendra K T User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Thunderbird/3.1.16 MIME-Version: 1.0 To: Marcelo Tosatti CC: Raghavendra K T , Greg Kroah-Hartman , KVM , Konrad Rzeszutek Wilk , Sedat Dilek , Virtualization , Jeremy Fitzhardinge , x86@kernel.org, "H. Peter Anvin" , Dave Jiang , Thomas Gleixner , Stefano Stabellini , Gleb Natapov , Yinghai Lu , Ingo Molnar , Avi Kivity , Rik van Riel , Xen , LKML , Srivatsa Vaddagiri , Peter Zijlstra , Sasha Levin , Suzuki Poulose , Dave Hansen , Jeremy Fitzhardinge Subject: Re: [PATCH RFC V3 2/4] kvm hypervisor : Add a hypercall to KVM hypervisor to support pv-ticketlocks References: <20111130085921.23386.89708.sendpatchset@oc5400248562.ibm.com> <20111130085959.23386.69166.sendpatchset@oc5400248562.ibm.com> <20111207104849.GA24849@amt.cnet> <4EDF5413.1030107@linux.vnet.ibm.com> <20111207123330.GA32212@amt.cnet> In-Reply-To: <20111207123330.GA32212@amt.cnet> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit x-cbid: 11120716-2674-0000-0000-0000028EE6AC Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/07/2011 06:03 PM, Marcelo Tosatti wrote: > On Wed, Dec 07, 2011 at 05:24:59PM +0530, Raghavendra K T wrote: >> On 12/07/2011 04:18 PM, Marcelo Tosatti wrote: >> Yes you are right. It was potentially racy and it was harmful too!. >> I had observed that it was stalling the CPU before I introduced >> kicked flag. >> >> But now, >> >> vcpu->kicked = 1 ==> kvm_make_request(KVM_REQ_UNHALT, vcpu); ==> > > Ok, please use a more descriptive name, such as "pvlock_kicked" or > something. > Yes, pvlock_kicked seems good. 'll use same unless something else flashes. >> >> __vcpu_run() ==> kvm_check_request(KVM_REQ_UNHALT, vcpu) ==> >> >> vcpuN->mp_state = KVM_MP_STATE_RUNNABLE; so eventually we will end up >> in RUNNABLE. >> >> Also Avi pointed that, logically kvm_arch_vcpu_ioctl_set_mpstate should >> be called only in vcpu thread, so after further debugging, I noticed >> that, setting vcpuN->mp_state = KVM_MP_STATE_RUNNABLE; is not >> necessary. >> I 'll remove that in the next patch. Thanks for pointing. > > In fact you don't need kvm_arch_vcpu_ioctl_set_mpstate either, only the > new "kicked" flag. > True indeed, I meant the same.