diff options
| author | Vitaly Kuznetsov <vkuznets@redhat.com> | 2022-03-25 14:21:40 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2022-04-08 14:40:38 +0200 |
| commit | 09c771c45c1243e295470225aaee726693fdc242 (patch) | |
| tree | 5dff772475210bd8c9c195a56a1270a68e3fb068 /virt | |
| parent | aea4ffdcf30fc625d5775798ee9862957d0421cb (diff) | |
| download | linux-stable-09c771c45c1243e295470225aaee726693fdc242.tar.gz linux-stable-09c771c45c1243e295470225aaee726693fdc242.tar.bz2 linux-stable-09c771c45c1243e295470225aaee726693fdc242.zip | |
KVM: x86: Forbid VMM to set SYNIC/STIMER MSRs when SynIC wasn't activated
commit b1e34d325397a33d97d845e312d7cf2a8b646b44 upstream.
Setting non-zero values to SYNIC/STIMER MSRs activates certain features,
this should not happen when KVM_CAP_HYPERV_SYNIC{,2} was not activated.
Note, it would've been better to forbid writing anything to SYNIC/STIMER
MSRs, including zeroes, however, at least QEMU tries clearing
HV_X64_MSR_STIMER0_CONFIG without SynIC. HV_X64_MSR_EOM MSR is somewhat
'special' as writing zero there triggers an action, this also should not
happen when SynIC wasn't activated.
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Message-Id: <20220325132140.25650-4-vkuznets@redhat.com>
Cc: stable@vger.kernel.org
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'virt')
0 files changed, 0 insertions, 0 deletions