diff options
| author | Sean Christopherson <[email protected]> | 2020-03-21 12:37:51 -0700 |
|---|---|---|
| committer | Paolo Bonzini <[email protected]> | 2020-03-23 15:44:26 -0400 |
| commit | 4f6ea0a87608e1b26ed26123ae7c42aaecdd2c6c (patch) | |
| tree | 4886e7cbf392f9d972ef374b6a778ef279cd0e80 /scripts/gcc-plugins/cyc_complexity_plugin.c | |
| parent | d260f9ef50c76c5587353fa71719be8cf5525f06 (diff) | |
KVM: VMX: Gracefully handle faults on VMXON
Gracefully handle faults on VMXON, e.g. #GP due to VMX being disabled by
BIOS, instead of letting the fault crash the system. Now that KVM uses
cpufeatures to query support instead of reading MSR_IA32_FEAT_CTL
directly, it's possible for a bug in a different subsystem to cause KVM
to incorrectly attempt VMXON[*]. Crashing the system is especially
annoying if the system is configured such that hardware_enable() will
be triggered during boot.
Oppurtunistically rename @addr to @vmxon_pointer and use a named param
to reference it in the inline assembly.
Print 0xdeadbeef in the ultra-"rare" case that reading MSR_IA32_FEAT_CTL
also faults.
[*] https://lkml.kernel.org/r/[email protected]
Signed-off-by: Sean Christopherson <[email protected]>
Message-Id: <[email protected]>
Reviewed-by: Vitaly Kuznetsov <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'scripts/gcc-plugins/cyc_complexity_plugin.c')
0 files changed, 0 insertions, 0 deletions