> On Feb 11, 2020, at 5:53 AM, Joerg Roedel <joro@xxxxxxxxxx> wrote: > > From: Tom Lendacky <thomas.lendacky@xxxxxxx> > > Implement a handler for #VC exceptions caused by VMMCALL instructions. > This patch is only a starting point, VMMCALL emulation under SEV-ES > needs further hypervisor-specific changes to provide additional state. > 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.
