| commit | 6d396b55203969ca61cc8f838db2e68433e13f7b | [log] [tgz] |
|---|---|---|
| author | Paolo Bonzini <pbonzini@redhat.com> | Wed Apr 01 14:25:33 2015 +0200 |
| committer | Paolo Bonzini <pbonzini@redhat.com> | Fri Jun 05 17:26:38 2015 +0200 |
| tree | 33dc0487be094936e88e9fe498a686cd679dd8d4 | |
| parent | 699023e239658e62da6f42f47d31b54788521ec1 [diff] |
KVM: x86: advertise KVM_CAP_X86_SMM ... and we're done. :) Because SMBASE is usually relocated above 1M on modern chipsets, and SMM handlers might indeed rely on 4G segment limits, we only expose it if KVM is able to run the guest in big real mode. This includes any of VMX+emulate_invalid_guest_state, VMX+unrestricted_guest, or SVM. Reviewed-by: Radim Krčmář <rkrcmar@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>