From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sasha Levin Subject: Re: [PATCH] KVM: Document KVM_NMI Date: Wed, 07 Dec 2011 14:37:14 +0200 Message-ID: <1323261434.4009.9.camel@lappy> References: <1323254613-29882-1-git-send-email-avi@redhat.com> <1323255728.4009.7.camel@lappy> <4EDF5843.6020005@redhat.com> <1323260448.4009.8.camel@lappy> <4EDF5CA1.2030102@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Marcelo Tosatti , kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from mail-ey0-f174.google.com ([209.85.215.174]:48349 "EHLO mail-ey0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755631Ab1LGMhe (ORCPT ); Wed, 7 Dec 2011 07:37:34 -0500 Received: by eaak14 with SMTP id k14so412379eaa.19 for ; Wed, 07 Dec 2011 04:37:33 -0800 (PST) In-Reply-To: <4EDF5CA1.2030102@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Wed, 2011-12-07 at 14:31 +0200, Avi Kivity wrote: > On 12/07/2011 02:20 PM, Sasha Levin wrote: > > On Wed, 2011-12-07 at 14:12 +0200, Avi Kivity wrote: > > > On 12/07/2011 01:02 PM, Sasha Levin wrote: > > > > I don't see the QEMU patch doing a stop before grabbing LAPIC state. Or > > > > does it happen somewhere before? > > > > > > It got dropped on the floor; it's now in next. > > > > I was talking about that patch you merged. I don't see where the vcpu is > > being paused before getting the LAPIC state. > > > > Oh, sorry. Well, once you exit from KVM_RUN, the vcpu is paused. > > It's really implied by the fact that vcpu ioctls must be issued from the > same thread. Oh, I totally forgot about that (here, and in my 'kvm nmi' patch). Thanks! -- Sasha.