From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3FA2770 for ; Wed, 19 May 2021 19:13:18 +0000 (UTC) X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 88F15AFAB; Wed, 19 May 2021 19:13:10 +0000 (UTC) Date: Wed, 19 May 2021 21:13:08 +0200 From: Joerg Roedel To: Peter Zijlstra Cc: Joerg Roedel , x86@kernel.org, Hyunwook Baek , hpa@zytor.com, Andy Lutomirski , Dave Hansen , Jiri Slaby , Dan Williams , Tom Lendacky , Juergen Gross , Kees Cook , David Rientjes , Cfir Cohen , Erdem Aktas , Masami Hiramatsu , Mike Stunes , Sean Christopherson , Martin Radev , Arvind Sankar , linux-coco@lists.linux.dev, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, virtualization@lists.linux-foundation.org Subject: Re: [PATCH v2 5/8] x86/sev-es: Leave NMI-mode before sending signals Message-ID: References: <20210519135251.30093-1-joro@8bytes.org> <20210519135251.30093-6-joro@8bytes.org> <20210519175450.GF21560@worktop.programming.kicks-ass.net> X-Mailing-List: linux-coco@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210519175450.GF21560@worktop.programming.kicks-ass.net> Hi Peter, thanks for your review. On Wed, May 19, 2021 at 07:54:50PM +0200, Peter Zijlstra wrote: > On Wed, May 19, 2021 at 03:52:48PM +0200, Joerg Roedel wrote: > > --- a/arch/x86/kernel/sev.c > > +++ b/arch/x86/kernel/sev.c > > @@ -1343,9 +1343,10 @@ DEFINE_IDTENTRY_VC_SAFE_STACK(exc_vmm_communication) > > return; > > } > > > > + instrumentation_begin(); > > + > > irq_state = irqentry_nmi_enter(regs); > > lockdep_assert_irqs_disabled(); > > - instrumentation_begin(); > > > > /* > > * This is invoked through an interrupt gate, so IRQs are disabled. The > > That's just plain wrong. No instrumentation is allowed before you enter > the exception context. Okay. > > + irqentry_nmi_exit(regs, irq_state); > > + > > And this is wrong too; because at this point the handler doesn't run in > _any_ context anymore, certainly not one you can call regular C code > from. The #VC handler is at this point not running on the IST stack anymore, but on the stack it came from or on the task stack. So my believe was that at this point it inherits the context it came from (just like the page-fault handler). But I also don't fully understand the context tracking, so is my assumption wrong? Regards, Joerg