Hi Min,
On Mon, Nov 1, 2021 at 6:16 AM Min Xu wrote:
>
> +VmTdExitHandleVe (
> + IN OUT EFI_EXCEPTION_TYPE *ExceptionType,
> + IN OUT EFI_SYSTEM_CONTEXT SystemContext
> + )
> +{
> + UINT64Status;
> + TD_RETURN_DATAReturnData;
> + EFI_SYSTEM_CONTEXT_X64
Hi, Gerd
> > +MmioExit (
> > + IN OUT EFI_SYSTEM_CONTEXT_X64 *Regs,
> > + IN TDCALL_VEINFO_RETURN_DATA *Veinfo
> > + )
> > +{
>
> > + do {
> > +OpCode = *Rip++;
> > +if (OpCode == 0x66) {
> > + OpSize = 2;
>
> Oh, wow. So the VE exit data doesn't provide the information
Hi,
> +MmioExit (
> + IN OUT EFI_SYSTEM_CONTEXT_X64 *Regs,
> + IN TDCALL_VEINFO_RETURN_DATA *Veinfo
> + )
> +{
> + do {
> +OpCode = *Rip++;
> +if (OpCode == 0x66) {
> + OpSize = 2;
Oh, wow. So the VE exit data doesn't provide the information which
io/mmio access actu
RFC： https://bugzilla.tianocore.org/show_bug.cgi?id=3429
The base VmgExitLib library provides a default limited interface to
handle #VE exception. To provide full support, the OVMF version of
VmgExitLib is extended to provide full support of #VE handler.
PcdIgnoreVeHalt is created in OvmfPkg.dec
