From: Denis Plotnikov <dplotnikov@virtuozzo.com>
To: pbonzini@redhat.com, rkrcmar@redhat.com, kvm@vger.kernel.org
Cc: rkagan@virtuozzo.com, den@virtuozzo.com, svt-core@lists.sw.ru
Subject: [PATCH v3 0/6] make L2's kvm-clock stable, get rid of pvclock_gtod
Date: Sat, 29 Jul 2017 15:35:05 +0300 [thread overview]
Message-ID: <1501331711-12961-1-git-send-email-dplotnikov@virtuozzo.com> (raw)
V3:
Changing the timekeeper interface for clocksource reading looks like
an overkill to achive the goal of getting cycles stamp for KVM.
Instead extend the timekeeping interface and add functions which provide
necessary data: read clocksource with cycles stamp, check whether the
clock source is stable.
Use those functions and improve existing timekeeper functionality to
replace pvclock_gtod_copy scheme in masterclock data calculation.
V2:
The main goal is to make L2 kvm-clock be stable when it's running over L1
with stable kvm-clock.
The patch series is for x86 architecture only. If the series is approved
I'll do changes for other architectures but I don't have an ability to
compile and check for every single on (help needed)
The patch series do the following:
* change timekeeper interface to get cycles stamp value from
the timekeeper
* get rid of pvclock copy in KVM by using the changed timekeeper
interface: get time and cycles right from the timekeeper
* make KVM recognize a stable kvm-clock as stable clocksource
and use the KVM masterclock in this case, which means making
L2 stable when running over stable L1 kvm-clock
Denis Plotnikov (6):
pvclock: add parameter to store cycles stamp to pvclock reading
function
KVM: x86: switch to masterclock update using timekeeper functionality
timekeeper: add clocksource change notifier
KVM: x86: remove not used pvclock_gtod_copy
pvclock: add clocksource change notification on changing of tsc stable
bit
kvmclock: add the clocksource stability querying function
arch/x86/include/asm/kvm_host.h | 2 +-
arch/x86/include/asm/pvclock.h | 2 +-
arch/x86/kernel/kvmclock.c | 26 ++++-
arch/x86/kernel/pvclock.c | 31 ++++-
arch/x86/kernel/tsc.c | 6 +
arch/x86/kvm/trace.h | 31 ++---
arch/x86/kvm/x86.c | 242 ++++++++--------------------------------
arch/x86/xen/time.c | 2 +-
include/linux/clocksource.h | 3 +
include/linux/cs_notifier.h | 17 +++
include/linux/timekeeping.h | 2 +
kernel/time/timekeeping.c | 72 +++++++++++-
12 files changed, 209 insertions(+), 227 deletions(-)
create mode 100644 include/linux/cs_notifier.h
--
2.7.4
next reply other threads:[~2017-07-29 12:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-29 12:35 Denis Plotnikov [this message]
2017-07-29 12:35 ` [PATCH v3 1/6] pvclock: add parameter to store cycles stamp to pvclock reading function Denis Plotnikov
2017-07-31 14:08 ` Paolo Bonzini
2017-07-29 12:35 ` [PATCH v3 2/6] KVM: x86: switch to masterclock update using timekeeper functionality Denis Plotnikov
2017-07-31 14:20 ` Paolo Bonzini
2017-08-01 9:30 ` Denis Plotnikov
2017-08-01 10:03 ` Paolo Bonzini
2017-08-01 10:16 ` Paolo Bonzini
2017-08-01 12:11 ` Denis Plotnikov
2017-08-01 12:28 ` Denis Plotnikov
2017-08-01 12:41 ` Paolo Bonzini
2017-08-01 12:46 ` Denis Plotnikov
2017-08-01 17:47 ` Radim Krčmář
2017-07-29 12:35 ` [PATCH v3 3/6] timekeeper: add clocksource change notifier Denis Plotnikov
2017-07-29 12:35 ` [PATCH v3 4/6] KVM: x86: remove not used pvclock_gtod_copy Denis Plotnikov
2017-07-29 12:35 ` [PATCH v3 5/6] pvclock: add clocksource change notification on changing of tsc stable bit Denis Plotnikov
2017-07-31 14:21 ` Paolo Bonzini
2017-07-29 12:35 ` [PATCH v3 6/6] kvmclock: add the clocksource stability querying function Denis Plotnikov
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=1501331711-12961-1-git-send-email-dplotnikov@virtuozzo.com \
--to=dplotnikov@virtuozzo.com \
--cc=den@virtuozzo.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkagan@virtuozzo.com \
--cc=rkrcmar@redhat.com \
--cc=svt-core@lists.sw.ru \
/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;
as well as URLs for NNTP newsgroup(s).