diff options
| author | Sean Christopherson <[email protected]> | 2024-02-09 22:16:59 +0000 |
|---|---|---|
| committer | Sean Christopherson <[email protected]> | 2024-04-09 17:24:36 +0000 |
| commit | a9466078687fb740298a52a095ee4832738efbea (patch) | |
| tree | da2e4f7ffb5df53ec85460f914098b69b97bd145 /arch/powerpc/lib/code-patching.c | |
| parent | KVM: nVMX: Clear EXIT_QUALIFICATION when injecting an EPT Misconfig (diff) | |
| download | kernel-a9466078687fb740298a52a095ee4832738efbea.tar.gz kernel-a9466078687fb740298a52a095ee4832738efbea.zip | |
KVM: x86: Move nEPT exit_qualification field from kvm_vcpu_arch to x86_exception
Move the exit_qualification field that is used to track information about
in-flight nEPT violations from "struct kvm_vcpu_arch" to "x86_exception",
i.e. associate the information with the actual nEPT violation instead of
the vCPU. To handle bits that are pulled from vmcs.EXIT_QUALIFICATION,
i.e. that are propagated from the "original" EPT violation VM-Exit, simply
grab them from the VMCS on-demand when injecting a nEPT Violation or a PML
Full VM-exit.
Aside from being ugly, having an exit_qualification field in kvm_vcpu_arch
is outright dangerous, e.g. see commit d7f0a00e438d ("KVM: VMX: Report
up-to-date exit qualification to userspace").
Opportunstically add a comment to call out that PML Full and EPT Violation
VM-Exits use the same bit to report NMI blocking information.
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Sean Christopherson <[email protected]>
Diffstat (limited to 'arch/powerpc/lib/code-patching.c')
0 files changed, 0 insertions, 0 deletions