diff options
| author | Zachary Amsden <zamsden@gmail.com> | 2012-02-03 17:43:56 (GMT) |
|---|---|---|
| committer | Avi Kivity <avi@redhat.com> | 2012-03-08 12:10:08 (GMT) |
| commit | 0dd6a6edb0124e6c71931ff575b18e15ed6e8603 (patch) | |
| tree | 758efc28e830eca71e3912a76315917037fadfee /scripts | |
| parent | f1e2b26003c41e581243c09ceed7567677449468 (diff) | |
| download | linux-0dd6a6edb0124e6c71931ff575b18e15ed6e8603.tar.xz | |
KVM: Dont mark TSC unstable due to S4 suspend
During a host suspend, TSC may go backwards, which KVM interprets
as an unstable TSC. Technically, KVM should not be marking the
TSC unstable, which causes the TSC clocksource to go bad, but we
need to be adjusting the TSC offsets in such a case.
Dealing with this issue is a little tricky as the only place we
can reliably do it is before much of the timekeeping infrastructure
is up and running. On top of this, we are not in a KVM thread
context, so we may not be able to safely access VCPU fields.
Instead, we compute our best known hardware offset at power-up and
stash it to be applied to all VCPUs when they actually start running.
Signed-off-by: Zachary Amsden <zamsden@gmail.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions