From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Tosatti Subject: Re: [PATCH RFC V3 2/4] kvm hypervisor : Add a hypercall to KVM hypervisor to support pv-ticketlocks Date: Wed, 7 Dec 2011 11:39:47 -0200 Message-ID: <20111207133947.GA1708@amt.cnet> 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> <4EDF6049.2030204@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <4EDF6049.2030204@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org To: Avi Kivity Cc: Raghavendra K T , x86@kernel.org, Peter Zijlstra , Virtualization , "H. Peter Anvin" , Stefano Stabellini , Xen , Dave Jiang , KVM , Raghavendra K T , Ingo Molnar , Rik van Riel , Konrad Rzeszutek Wilk , Srivatsa Vaddagiri , Jeremy Fitzhardinge , Sasha Levin , Sedat Dilek , Thomas Gleixner , Yinghai Lu , Greg Kroah-Hartman , LKML , Dave Hansen , Suzuk List-Id: virtualization@lists.linuxfoundation.org On Wed, Dec 07, 2011 at 02:47:05PM +0200, Avi Kivity wrote: > On 12/07/2011 02:33 PM, Marcelo Tosatti wrote: > > > > > > 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. > > If we have a kicked flag, it becomes necessary to live migrate it. > > Maybe we can change KVM_GET_MP_STATE to fold the kicked flag into the mp > state (converting HALTED into RUNNABLE). Yep, that works. > Also I think we can keep the kicked flag in vcpu->requests, no need for > new storage. Was going to suggest it but it violates the currently organized processing of entries at the beginning of vcpu_enter_guest. That is, this "kicked" flag is different enough from vcpu->requests processing that a separate variable seems worthwhile (even more different with convertion to MP_STATE at KVM_GET_MP_STATE).