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
