From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from theia.8bytes.org (8bytes.org [81.169.241.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BC34B2FB2 for ; Fri, 11 Jun 2021 14:20:44 +0000 (UTC) Received: by theia.8bytes.org (Postfix, from userid 1000) id 4D7A52FA; Fri, 11 Jun 2021 16:20:37 +0200 (CEST) Date: Fri, 11 Jun 2021 16:20:36 +0200 From: Joerg Roedel To: Borislav Petkov Cc: x86@kernel.org, Joerg Roedel , hpa@zytor.com, Andy Lutomirski , Dave Hansen , Peter Zijlstra , 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 v4 2/6] x86/sev-es: Disable IRQs while GHCB is active Message-ID: References: <20210610091141.30322-1-joro@8bytes.org> <20210610091141.30322-3-joro@8bytes.org> 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: On Fri, Jun 11, 2021 at 04:05:15PM +0200, Borislav Petkov wrote: > On Thu, Jun 10, 2021 at 11:11:37AM +0200, Joerg Roedel wrote: > Why not simply "sandwich" them: > > local_irq_save() > sev_es_get_ghcb() > > ...blablabla > > sev_es_put_ghcb() > local_irq_restore(); > > in every call site? I am not a fan of this, because its easily forgotten to add local_irq_save()/local_irq_restore() calls around those. Yes, we can add irqs_disabled() assertions to the functions, but we can as well just disable/enable IRQs in them. Only the previous value of EFLAGS.IF needs to be carried from one function to the other. > Hmm, so why aren't you accessing/setting data->ghcb_active and > data->backup_ghcb_active safely using cmpxchg() if this path can be > interrupted by an NMI? Using cmpxchg is not necessary here. It is all per-cpu data, so local to the current cpu. If an NMI happens anywhere in sev_es_get_ghcb() it can still use the GHCB, because the interrupted #VC handler will not start writing to it before sev_es_get_ghcb() returned. Problems only come up when one path starts writing to the GHCB, but that happens long after it is marked active. Regards, Joerg