diff options
| author | Sean Christopherson <seanjc@google.com> | 2022-01-20 04:07:18 +0300 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2022-01-26 20:15:01 +0300 |
| commit | 3280cc22aea74d78ebbea277ff8bc8d593582de3 (patch) | |
| tree | de291251903e4c7c7af2d79f7069976690d96b1e /scripts/gdb/linux/modules.py | |
| parent | 04c40f344defdbd842d8a64fcfb47ef74b39ef4e (diff) | |
| download | linux-3280cc22aea74d78ebbea277ff8bc8d593582de3.tar.xz | |
KVM: SVM: Don't apply SEV+SMAP workaround on code fetch or PT access
Resume the guest instead of synthesizing a triple fault shutdown if the
instruction bytes buffer is empty due to the #NPF being on the code fetch
itself or on a page table access. The SMAP errata applies if and only if
the code fetch was successful and ucode's subsequent data read from the
code page encountered a SMAP violation. In practice, the guest is likely
hosed either way, but crashing the guest on a code fetch to emulated MMIO
is technically wrong according to the behavior described in the APM.
Signed-off-by: Sean Christopherson <seanjc@google.com>
Reviewed-by: Liam Merwick <liam.merwick@oracle.com>
Message-Id: <20220120010719.711476-9-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'scripts/gdb/linux/modules.py')
0 files changed, 0 insertions, 0 deletions
