From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joerg Roedel Subject: Re: [PATCH 50/62] x86/sev-es: Handle VMMCALL Events Date: Wed, 12 Feb 2020 14:22:20 +0100 Message-ID: <20200212132220.GI20066@8bytes.org> References: <20200211135256.24617-51-joro@8bytes.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Andy Lutomirski Cc: x86@kernel.org, hpa@zytor.com, Andy Lutomirski , Dave Hansen , Peter Zijlstra , Thomas Hellstrom , Jiri Slaby , Dan Williams , Tom Lendacky , Juergen Gross , Kees Cook , linux-kernel@vger.kernel.org, kvm@vger.kernel.org, virtualization@lists.linux-foundation.org, Joerg Roedel List-Id: virtualization@lists.linuxfoundation.org On Tue, Feb 11, 2020 at 04:14:53PM -0800, Andy Lutomirski wrote: > > How about we just don’t do VMMCALL if we’re a SEV-ES guest? Otherwise > we add thousands of cycles of extra latency for no good reason. True, but I left that as a future optimization for now, given the size the patch-set already has. The idea is to add an abstraction around VMMCALL for the support code of the various hypervisors and just do a VMGEXIT in that wrapper when in an SEV-ES guest. But again, that is a separate patch-set. Regards, Joerg