From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joerg Roedel Subject: Re: [PATCH 40/70] x86/sev-es: Setup per-cpu GHCBs for the runtime handler Date: Wed, 15 Apr 2020 17:54:28 +0200 Message-ID: <20200415155428.GE21899@suse.de> References: <20200319091407.1481-1-joro@8bytes.org> <20200319091407.1481-41-joro@8bytes.org> <09757a84-1d81-74d5-c425-cff241f02ab9@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <09757a84-1d81-74d5-c425-cff241f02ab9@amd.com> Sender: linux-kernel-owner@vger.kernel.org To: Tom Lendacky Cc: Mike Stunes , Joerg Roedel , "x86@kernel.org" , "hpa@zytor.com" , Andy Lutomirski , Dave Hansen , Peter Zijlstra , Thomas Hellstrom , Jiri Slaby , Dan Williams , Juergen Gross , Kees Cook , "linux-kernel@vger.kernel.org" , "kvm@vger.kernel.org" , "virtualization@lists.linux-foundation.org" List-Id: virtualization@lists.linuxfoundation.org On Tue, Apr 14, 2020 at 03:04:42PM -0500, Tom Lendacky wrote: > At that point the guest won't be able to communicate with the hypervisor, > too. Maybe we should BUG() here to terminate further processing? We could talk to the hypervisor, there is still the boot-GHCB in the bss-decrypted section. But there is nothing that could be done here anyway besides terminating the guest. Regards, Joerg