[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1473200999-123004-1-git-send-email-pbonzini@redhat.com>
Date: Wed, 7 Sep 2016 00:29:57 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: linux-kernel@...r.kernel.org, kvm@...r.kernel.org
Cc: rkrcmar@...hat.com, dmatlack@...gle.com, luto@...nel.org,
peterhornyack@...gle.com, x86@...nel.org
Subject: [PATCH v2 0/2] if running under KVM, use kvmclock to compute TSC deadline value
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
Powered by blists - more mailing lists