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 RFC 0/2] KVM: x86: Support using the VMX preemption timer for APIC Timer periodic/oneshot mode
Date: Tue, 11 Oct 2016 20:17:18 +0800 [thread overview]
Message-ID: <1476188240-3502-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 support using the VMX preemption timer for APIC Timer
periodic/oneshot mode.
I add a print in oneshot mode testcase of kvm-unit-tests/apic.flat and observed
that w/ patch the latency is ~2% of w/o patch. I think maybe something is still
not right in the patchset, in addition, tmcct in apic_get_tmcct() maybe is not
calculated correctly. Your comments to improve the patchset is a great appreciated.
Wanpeng Li (2):
KVM: lapic: Extract start_sw_period() to handle oneshot/periodic mode
KVM: x86: Support using the vmx preemption timer for APIC Timer periodic/one mode
arch/x86/kvm/lapic.c | 162 ++++++++++++++++++++++++++++++---------------------
1 file changed, 95 insertions(+), 67 deletions(-)
--
1.9.1
next reply other threads:[~2016-10-11 12:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 12:17 Wanpeng Li [this message]
2016-10-11 12:17 ` [PATCH RFC 1/2] KVM: lapic: Extract start_sw_period() to handle " Wanpeng Li
2016-10-11 12:17 ` [PATCH RFC 2/2] KVM: x86: Support using the VMX preemption timer for APIC Timer " Wanpeng Li
2016-10-11 15:06 ` Radim Krčmář
2016-10-12 8:35 ` Wanpeng Li
2017-07-11 0:13 ` [PATCH RFC 0/2] " Andy Lutomirski
2017-07-11 2:43 ` Wanpeng Li
2017-07-11 14:40 ` Andy Lutomirski
2017-07-11 7:43 ` Paolo Bonzini
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=1476188240-3502-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®