diff options
author | Hou Wenlong <houwenlong.hwl@antgroup.com> | 2022-03-07 20:26:33 +0800 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2022-04-02 05:34:47 -0400 |
commit | ac8d6cad3c7b39633d5899dc2fa9abec7135e83e (patch) | |
tree | 6945076bc75b5369bb1ab93bf56b0d891fd0c605 /arch/x86/kernel/eisa.c | |
parent | a836839cbfe60dc434c5476a7429cf2bae36415d (diff) | |
download | linux-ac8d6cad3c7b39633d5899dc2fa9abec7135e83e.tar.gz |
KVM: x86: Only do MSR filtering when access MSR by rdmsr/wrmsr
If MSR access is rejected by MSR filtering, kvm_set_msr()/kvm_get_msr() would return KVM_MSR_RET_FILTERED, and the return value is only handled well for rdmsr/wrmsr. However, some instruction emulation and state transition also use kvm_set_msr()/kvm_get_msr() to do msr access but may trigger some unexpected results if MSR access is rejected, E.g. RDPID emulation would inject a #UD but RDPID wouldn't cause a exit when RDPID is supported in hardware and ENABLE_RDTSCP is set. And it would also cause failure when load MSR at nested entry/exit. Since msr filtering is based on MSR bitmap, it is better to only do MSR filtering for rdmsr/wrmsr. Signed-off-by: Hou Wenlong <houwenlong.hwl@antgroup.com> Message-Id: <2b2774154f7532c96a6f04d71c82a8bec7d9e80b.1646655860.git.houwenlong.hwl@antgroup.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'arch/x86/kernel/eisa.c')
0 files changed, 0 insertions, 0 deletions