summaryrefslogtreecommitdiffstats
path: root/arch/m68k/Kconfig.cpu
diff options
context:
space:
mode:
authorYunhong Jiang <yunhong.jiang@gmail.com>2016-06-13 14:20:01 -0700
committerPaolo Bonzini <pbonzini@redhat.com>2016-06-16 10:07:48 +0200
commitce7a058a2117f0bca2f42f2870a97bfa9aa8e099 (patch)
tree7d0766fef470bae200c100b94b996273f73193eb /arch/m68k/Kconfig.cpu
parent53f9eedff713bab262b64682ad1abb1e8116d041 (diff)
downloadblackbird-op-linux-ce7a058a2117f0bca2f42f2870a97bfa9aa8e099.tar.gz
blackbird-op-linux-ce7a058a2117f0bca2f42f2870a97bfa9aa8e099.zip
KVM: x86: support using the vmx preemption timer for tsc deadline timer
The VMX preemption timer can be used to virtualize the TSC deadline timer. The VMX preemption timer is armed when the vCPU is running, and a VMExit will happen if the virtual TSC deadline timer expires. When the vCPU thread is blocked because of HLT, KVM will switch to use an hrtimer, and then go back to the VMX preemption timer when the vCPU thread is unblocked. This solution avoids the complex OS's hrtimer system, and the host timer interrupt handling cost, replacing them with a little math (for guest->host TSC and host TSC->preemption timer conversion) and a cheaper VMexit. This benefits latency for isolated pCPUs. [A word about performance... Yunhong reported a 30% reduction in average latency from cyclictest. I made a similar test with tscdeadline_latency from kvm-unit-tests, and measured - ~20 clock cycles loss (out of ~3200, so less than 1% but still statistically significant) in the worst case where the test halts just after programming the TSC deadline timer - ~800 clock cycles gain (25% reduction in latency) in the best case where the test busy waits. I removed the VMX bits from Yunhong's patch, to concentrate them in the next patch - Paolo] Signed-off-by: Yunhong Jiang <yunhong.jiang@intel.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'arch/m68k/Kconfig.cpu')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud