From: Wanpeng Li <kernellwp@gmail.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Yunhong Jiang" <yunhong.jiang@intel.com>,
"Wanpeng Li" <wanpeng.li@hotmail.com>
Subject: [PATCH 0/5] KVM: LAPIC: Add APIC Timer periodic/oneshot mode VMX preemption timer support
Date: Mon, 17 Oct 2016 15:44:57 +0800 [thread overview]
Message-ID: <1476690302-22158-1-git-send-email-wanpeng.li@hotmail.com> (raw)
Most windows guests which I have on hand currently still utilize APIC Timer
periodic/oneshot mode instead of APIC Timer tsc-deadline mode:
- windows 2008 server r2
- windows 2012 server r2
- windows 7
- windows 10
This patchset adds the APIC Timer periodic/oneshot mode VMX preemption
timer support.
I test the patchset by adding kvm-unit-test/apic_timer_latency.flat to test 100 thousands
times APIC timer operations.
The patchset reduces ~3800+ clock cycles for each APIC timer periodic mode
operation virtualization.
V1 -> RFC v3:
* squash patch 3 into patch 6
* fix switch sw to hv timer
RFC v2 -> RFC v3:
* remove kvm_lapic_hv_timer_in_use() check in apic_get_tmcc, replace
the hritmer_get_remaining() by target_expiration - now
* rename expired_period to target_expiration
* introduce set_target_expiration() helper
* move the checking of minimal period to set_target_expiration()
* cleanup kvm_get_lapic_target_deadline_tsc()
RFC v1 -> RFC v2:
* remember the timeout when setting up the timer to get a correct TMCCT
* move apic->lapic_timer.period/tscdeadline caculations to start_apic_timer()
Wanpeng Li (5):
KVM: LAPIC: extract start_sw_period() to handle periodic/oneshot mode
KVM: LAPIC: guarantee the timer is in tsc-deadline mode when rdmsr MSR_IA32_TSCDEADLINE
KVM: LAPIC: introduce kvm_get_lapic_target_expiration_tsc()
KVM: LAPIC: rename start/cancel_hv_tscdeadline to start/cancel_hv_timer
KVM: LAPIC: add APIC Timer periodic/oneshot mode VMX preemption timer support
arch/x86/kvm/lapic.c | 193 +++++++++++++++++++++++++++++++++------------------
arch/x86/kvm/lapic.h | 2 +
arch/x86/kvm/x86.c | 2 +-
3 files changed, 129 insertions(+), 68 deletions(-)
--
1.9.1
next reply other threads:[~2016-10-17 7:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 7:44 Wanpeng Li [this message]
2016-10-17 7:44 ` [PATCH 1/5] KVM: LAPIC: extract start_sw_period() to handle periodic/oneshot mode Wanpeng Li
2016-10-17 7:44 ` [PATCH 2/5] KVM: LAPIC: guarantee the timer is in tsc-deadline mode Wanpeng Li
2016-10-17 7:45 ` [PATCH 3/5] KVM: LAPIC: introduce kvm_get_lapic_target_expiration_tsc() Wanpeng Li
2016-10-17 7:45 ` [PATCH 4/5] KVM: LAPIC: rename start/cancel_hv_tscdeadline to start/cancel_hv_timer Wanpeng Li
2016-10-17 7:45 ` [PATCH 5/5] KVM: LAPIC: add APIC Timer periodic/oneshot mode VMX preemption timer support Wanpeng Li
2016-10-17 8:45 ` Paolo Bonzini
2016-10-19 19:28 ` Radim Krčmář
2016-10-19 22:57 ` Wanpeng Li
2016-10-20 18:10 ` Radim Krčmář
2016-10-21 13:38 ` Wanpeng Li
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1476690302-22158-1-git-send-email-wanpeng.li@hotmail.com \
--to=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=wanpeng.li@hotmail.com \
--cc=yunhong.jiang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®