diff options
author | Paolo Bonzini <pbonzini@redhat.com> | 2022-03-24 09:21:41 +0100 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2022-03-24 18:30:46 +0100 |
commit | 5286c3662294119dc2dd1e9296757337211451f6 (patch) | |
tree | 287d45628f5b747073ff304c301821331e220c55 /.readthedocs.yml | |
parent | de65b39a517c9977769c612af716dc418ce2ea0b (diff) |
target/i386: properly reset TSC on reset
Some versions of Windows hang on reboot if their TSC value is greater
than 2^54. The calibration of the Hyper-V reference time overflows
and fails; as a result the processors' clock sources are out of sync.
The issue is that the TSC _should_ be reset to 0 on CPU reset and
QEMU tries to do that. However, KVM special cases writing 0 to the
TSC and thinks that QEMU is trying to hot-plug a CPU, which is
correct the first time through but not later. Thwart this valiant
effort and reset the TSC to 1 instead, but only if the CPU has been
run once.
For this to work, env->tsc has to be moved to the part of CPUArchState
that is not zeroed at the beginning of x86_cpu_reset.
Reported-by: Vadim Rozenfeld <vrozenfe@redhat.com>
Supersedes: <20220324082346.72180-1-pbonzini@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to '.readthedocs.yml')
0 files changed, 0 insertions, 0 deletions