summaryrefslogtreecommitdiffstats
path: root/net/irda
diff options
context:
space:
mode:
authorZachary Amsden <zamsden@gmail.com>2012-02-03 15:43:54 -0200
committerAvi Kivity <avi@redhat.com>2012-03-08 14:10:06 +0200
commit6f526ec5383dcd5fa5ffc7b3ac1d62099a0b46ad (patch)
tree3493dcd8ee803f1c8c77dd505d02816b2fc449e3 /net/irda
parentb183aa580a3a09b5d79224a9022418508532c778 (diff)
downloadlinux-stable-6f526ec5383dcd5fa5ffc7b3ac1d62099a0b46ad.tar.gz
linux-stable-6f526ec5383dcd5fa5ffc7b3ac1d62099a0b46ad.tar.bz2
linux-stable-6f526ec5383dcd5fa5ffc7b3ac1d62099a0b46ad.zip
KVM: Add last_host_tsc tracking back to KVM
The variable last_host_tsc was removed from upstream code. I am adding it back for two reasons. First, it is unnecessary to use guest TSC computation to conclude information about the host TSC. The guest may set the TSC backwards (this case handled by the previous patch), but the computation of guest TSC (and fetching an MSR) is significanlty more work and complexity than simply reading the hardware counter. In addition, we don't actually need the guest TSC for any part of the computation, by always recomputing the offset, we can eliminate the need to deal with the current offset and any scaling factors that may apply. The second reason is that later on, we are going to be using the host TSC value to restore TSC offsets after a host S4 suspend, so we need to be reading the host values, not the guest values here. 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 'net/irda')
0 files changed, 0 insertions, 0 deletions