From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Denis Plotnikov <dplotnikov@virtuozzo.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, rkagan@virtuozzo.com, den@virtuozzo.com,
svt-core@lists.sw.ru
Subject: Re: [PATCH v3 2/6] KVM: x86: switch to masterclock update using timekeeper functionality
Date: Tue, 1 Aug 2017 19:47:35 +0200 [thread overview]
Message-ID: <20170801174734.GB316@flask> (raw)
In-Reply-To: <c93e557f-7cf8-ad4b-eb57-e012ebf809a3@virtuozzo.com>
2017-08-01 15:46+0300, Denis Plotnikov:
> Patches are in progress.
> They well be sent soon, nice and shiny!
Please Cc timekeeper and x86 people too, thanks!
next prev parent reply other threads:[~2017-08-01 17:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-29 12:35 [PATCH v3 0/6] make L2's kvm-clock stable, get rid of pvclock_gtod Denis Plotnikov
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ář [this message]
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=20170801174734.GB316@flask \
--to=rkrcmar@redhat.com \
--cc=den@virtuozzo.com \
--cc=dplotnikov@virtuozzo.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkagan@virtuozzo.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).