diff options
| author |   Paolo Bonzini <pbonzini@redhat.com> | 2020-09-24 14:45:27 +0200 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2020-09-28 07:59:52 -0400 |
| commit | 0c899c25d754ae386940f0e1b86b31d3921480b6 (patch) | |
| tree | f88648c3c9ef85bbc14a3da9bb9688ebb386ccef /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | KVM: nSVM: delay MSR permission processing to first nested VM run (diff) | |
| download | wireguard-linux-0c899c25d754ae386940f0e1b86b31d3921480b6.tar.xz wireguard-linux-0c899c25d754ae386940f0e1b86b31d3921480b6.zip | |
KVM: x86: do not attempt TSC synchronization on guest writes
KVM special-cases writes to MSR_IA32_TSC so that all CPUs have
the same base for the TSC. This logic is complicated, and we
do not want it to have any effect once the VM is started.
In particular, if any guest started to synchronize its TSCs
with writes to MSR_IA32_TSC rather than MSR_IA32_TSC_ADJUST,
the additional effect of kvm_write_tsc code would be uncharted
territory.
Therefore, this patch makes writes to MSR_IA32_TSC behave
essentially the same as writes to MSR_IA32_TSC_ADJUST when
they come from the guest. A new selftest (which passes
both before and after the patch) checks the current semantics
of writes to MSR_IA32_TSC and MSR_IA32_TSC_ADJUST originating
from both the host and the guest.
Upcoming work to remove the special side effects
of host-initiated writes to MSR_IA32_TSC and MSR_IA32_TSC_ADJUST
will be able to build onto this test, adjusting the host side
to use the new APIs and achieve the same effect.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions