Oliver Upton 828ca89628 KVM: x86: Expose TSC offset controls to userspace ... To date, VMM-directed TSC synchronization and migration has been a bit messy. KVM has some baked-in heuristics around TSC writes to infer if the VMM is attempting to synchronize. This is problematic, as it depends on host userspace writing to the guest's TSC within 1 second of the last write. A much cleaner approach to configuring the guest's views of the TSC is to simply migrate the TSC offset for every vCPU. Offsets are idempotent, and thus not subject to change depending on when the VMM actually reads/writes values from/to KVM. The VMM can then read the TSC once with KVM_GET_CLOCK to capture a (realtime, host_tsc) pair at the instant when the guest is paused. Cc: David Matlack <dmatlack@google.com> Cc: Sean Christopherson <seanjc@google.com> Signed-off-by: Oliver Upton <oupton@google.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Message-Id: <20210916181538.968978-8-oupton@google.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>		2021-10-18 14:43:45 -04:00
..
acrn	docs: acrn: Introduce ACRN	2021-02-09 10:58:18 +01:00
kvm	KVM: x86: Expose TSC offset controls to userspace	2021-10-18 14:43:45 -04:00
uml	docs: virt: user_mode_linux_howto_v2.rst: fix a literal block markup	2020-10-16 07:28:20 +02:00
guest-halt-polling.rst	docs: virt: guest-halt-polling.txt convert to ReST	2020-02-12 20:10:08 +01:00
index.rst	docs: acrn: Introduce ACRN	2021-02-09 10:58:18 +01:00
ne_overview.rst	nitro_enclaves: Add overview documentation	2020-09-22 13:58:41 +02:00
paravirt_ops.rst