From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joerg Roedel Subject: Re: [PATCH 1/8] KVM: SVM: Fix nested nmi handling Date: Fri, 23 Apr 2010 16:31:59 +0200 Message-ID: <20100423143159.GJ31537@amd.com> References: <1271932394-13968-1-git-send-email-joerg.roedel@amd.com> <1271932394-13968-2-git-send-email-joerg.roedel@amd.com> <622FCBB5-826D-4392-A521-7E395507398B@suse.de> <20100423141355.GD31537@amd.com> <85D89C34-806C-4376-89BA-5BFD413F5396@suse.de> <20100423142258.GG31537@amd.com> <013159C3-277C-447C-B64B-D2196AF851F9@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: Avi Kivity , Marcelo Tosatti , kvm@vger.kernel.org, linux-kernel@vger.kernel.org To: Alexander Graf Return-path: Received: from tx2ehsobe004.messaging.microsoft.com ([65.55.88.14]:50243 "EHLO TX2EHSOBE008.bigfish.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753258Ab0DWOcr (ORCPT ); Fri, 23 Apr 2010 10:32:47 -0400 Content-Disposition: inline In-Reply-To: <013159C3-277C-447C-B64B-D2196AF851F9@suse.de> Sender: kvm-owner@vger.kernel.org List-ID: On Fri, Apr 23, 2010 at 04:24:54PM +0200, Alexander Graf wrote: > > On 23.04.2010, at 16:22, Joerg Roedel wrote: > > No, nested_svm_nmi runs in atomic context where we can't emulate a > > vmexit. We set exit_required and emulate the vmexit later. > > So we modify the L2 rflags and then trigger a #vmexit, leaving the l2 > state broken? No, the rflags are changed in enable_nmi_window which isn't called when we run nested and the nested hypervisor intercepts nmi. So it only runs in the !nested case where it can't corrupt L2 state. Joerg