From: Paolo Bonzini <pbonzini@redhat.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: rkrcmar@redhat.com, dmatlack@google.com, luto@kernel.org,
peterhornyack@google.com, x86@kernel.org
Subject: [PATCH v2 0/2] if running under KVM, use kvmclock to compute TSC deadline value
Date: Wed, 7 Sep 2016 00:29:57 +0200 [thread overview]
Message-ID: <1473200999-123004-1-git-send-email-pbonzini@redhat.com> (raw)
v1 posted here: https://patchwork.kernel.org/patch/9214993/
The motivation for this patch is in patch 2 (or you can read it from v1).
This version is larger but the hooks into apic.c are cleaner than in
v1. Instead of arranging for kvmclock to replace only a small part of
setup_apic_timer, it registers its own clockevent. The downside is that
kvmclock now needs to hook into the LAPIC timer interrupt to invoke the
event_handler of the new clockevent, but this is pretty straightforward
with a new pvop (assuming the introduction of new pvops is straightforward
at all).
Thanks,
Paolo
Paolo Bonzini (2):
x86: paravirt: add local_apic_timer_interrupt to pv_ops
x86, kvm: use kvmclock to compute TSC deadline value
arch/x86/include/asm/apic.h | 2 +
arch/x86/include/asm/paravirt.h | 5 ++
arch/x86/include/asm/paravirt_types.h | 1 +
arch/x86/kernel/apic/apic.c | 4 +-
arch/x86/kernel/kvmclock.c | 156 ++++++++++++++++++++++++++++++++++
arch/x86/kernel/paravirt.c | 1 +
6 files changed, 167 insertions(+), 2 deletions(-)
--
1.8.3.1
next reply other threads:[~2016-09-06 22:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 22:29 Paolo Bonzini [this message]
2016-09-06 22:29 ` [PATCH 1/2] x86: paravirt: add local_apic_timer_interrupt to pv_ops Paolo Bonzini
2016-09-07 6:25 ` kbuild test robot
2016-09-07 6:33 ` kbuild test robot
2016-09-06 22:29 ` [PATCH 2/2] x86, kvm: use kvmclock to compute TSC deadline value Paolo Bonzini
2016-09-08 22:13 ` David Matlack
2016-09-09 16:38 ` Paolo Bonzini
2016-09-09 20:05 ` David Matlack
2016-10-11 4:05 ` Wanpeng Li
2016-09-15 15:09 ` Radim Krčmář
2016-09-15 16:00 ` Paolo Bonzini
2016-09-15 19:59 ` Radim Krčmář
2016-09-15 21:02 ` Paolo Bonzini
2016-09-16 14:59 ` Radim Krčmář
2016-09-16 15:06 ` Paolo Bonzini
2016-09-16 15:24 ` Radim Krčmář
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=1473200999-123004-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=dmatlack@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterhornyack@google.com \
--cc=rkrcmar@redhat.com \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.