diff options
| author | Wanpeng Li <wanpengli@tencent.com> | 2018-05-05 04:02:32 -0700 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2018-05-15 11:56:21 +0200 |
| commit | 4c27625b7a67eb9006963ed2bcf8e53b259b43af (patch) | |
| tree | 232f21838dfcd43a6ee929f9c456816c7e20d19b /virt | |
| parent | 64f7a11586ab9262f00b8b6eceef6d8154921bd8 (diff) | |
| download | linux-0-day-4c27625b7a67eb9006963ed2bcf8e53b259b43af.tar.gz linux-0-day-4c27625b7a67eb9006963ed2bcf8e53b259b43af.tar.xz | |
KVM: X86: Lower the default timer frequency limit to 200us
Anthoine reported:
The period used by Windows change over time but it can be 1
milliseconds or less. I saw the limit_periodic_timer_frequency
print so 500 microseconds is sometimes reached.
As suggested by Paolo, lower the default timer frequency limit to a
smaller interval of 200 us (5000 Hz) to leave some headroom. This
is required due to Windows 10 changing the scheduler tick limit
from 1024 Hz to 2048 Hz.
Reported-by: Anthoine Bourgeois <anthoine.bourgeois@blade-group.com>
Suggested-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Darren Kenny <darren.kenny@oracle.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: Radim Krčmář <rkrcmar@redhat.com>
Cc: Anthoine Bourgeois <anthoine.bourgeois@blade-group.com>
Cc: Darren Kenny <darren.kenny@oracle.com>
Cc: Jan Kiszka <jan.kiszka@web.de>
Signed-off-by: Wanpeng Li <wanpengli@tencent.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'virt')
0 files changed, 0 insertions, 0 deletions