I haven't done the WriteIdtr() stuff, yet, but the passing of the SEV-ES status from the ResetVector code to the SEC code via the SEV-ES page at 0x0080_B000 is working nicely. Thanks, Tom

#vc

BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=2198 Add base support to handle #VC exceptions. This includes a stub routine to invoke when a #VC exception occurs and special checks in the common e

#vc

It's all on the guest side. That's not the issue, the issue is (again) complexity, and possibly also the limited expressiveness of the S3 boot script "language" (the set of opcodes). Roughly, this is

#vc

From: Tom Lendacky <thomas.lendacky@...> BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=2198 An SEV-ES guest will generate a #VC exception when it encounters a non-automatic exit (NAE) event.

#vc

From: Tom Lendacky <thomas.lendacky@...> BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=2198 Add base support to handle #VC exceptions. This includes a stub routine to invoke when a #VC except

#vc

From: Tom Lendacky <thomas.lendacky@...> Add base support to handle #VC exceptions. This includes a stub routine to invoke when a #VC exception occurs and special checks in the common exception ha

#vc

From: Tom Lendacky <thomas.lendacky@...> An SEV-ES guest will generate a #VC exception when it encounters a non-automatic exit (NAE) event. It is expected that the #VC exception handler will commu

#vc

From: Tom Lendacky <thomas.lendacky@...> A per-CPU implementation for holding values specific to a CPU when running as an SEV-ES guest, specifically to hold the Debug Register value. Allocate an e

#vc

From: Tom Lendacky <thomas.lendacky@...> An SEV-ES guest will generate a #VC exception when it encounters a non-automatic exit (NAE) event. It is expected that the #VC exception handler will commu

#vc