aboutsummaryrefslogtreecommitdiffstats
path: root/scripts
diff options
context:
space:
mode:
authorJon Doron <arilou@gmail.com>2020-07-17 15:52:38 +0300
committerPaolo Bonzini <pbonzini@redhat.com>2020-08-10 13:22:10 -0400
commit99b48ecc8e800983b6e00a2350daaeceba1f7406 (patch)
tree735f7bb8cf487e64d5e5f2ae795d2c13dfef8600 /scripts
parentMIPS: KVM: Convert a fallthrough comment to fallthrough (diff)
downloadlinux-dev-99b48ecc8e800983b6e00a2350daaeceba1f7406.tar.xz
linux-dev-99b48ecc8e800983b6e00a2350daaeceba1f7406.zip
x86/kvm/hyper-v: Synic default SCONTROL MSR needs to be enabled
Based on an analysis of the HyperV firmwares (Gen1 and Gen2) it seems like the SCONTROL is not being set to the ENABLED state as like we have thought. Also from a test done by Vitaly Kuznetsov, running a nested HyperV it was concluded that the first access to the SCONTROL MSR with a read resulted with the value of 0x1, aka HV_SYNIC_CONTROL_ENABLE. It's important to note that this diverges from the value states in the HyperV TLFS of 0. Signed-off-by: Jon Doron <arilou@gmail.com> Message-Id: <20200717125238.1103096-2-arilou@gmail.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions