From: Denis Plotnikov <dplotnikov@virtuozzo.com>
To: <pbonzini@redhat.com>, <rkrcmar@redhat.com>,
<mtosatti@redhat.com>, <kvm@vger.kernel.org>
Cc: <rkagan@virtuozzo.com>, <den@virtuozzo.com>, <dplotnikov@virtuozzo.com>
Subject: [PATCH v2 0/2] maintaining of kvm_clock stability on guest vCPU hotplug
Date: Fri, 7 Apr 2017 12:06:45 +0300 [thread overview]
Message-ID: <1491556007-56332-1-git-send-email-dplotnikov@virtuozzo.com> (raw)
new in v2:
- fix possible wraparound on the synchronization detection
- lines exceeding 80 chars are re-formatted
- excess parentheses are removed
======================
It was found, that after adding a new vCPU to a running VM (CPU hotplug)
kvm_clock lost the stability property in case of using it. This happened
because KVM didn't treated cpu hotplug as a special case of TSC
synchronization.
This patch series adds cpu hotplug to the TSC synchronization cases.
Denis Plotnikov (2):
KVM: x86: remaster kvm_write_tsc code
KVM: x86: fix maintaining of kvm_clock stability on guest CPU hotplug
arch/x86/kvm/x86.c | 61 ++++++++++++++++++++----------------------------------
1 file changed, 22 insertions(+), 39 deletions(-)
--
1.8.3.1
next reply other threads:[~2017-04-07 9:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 9:06 Denis Plotnikov [this message]
2017-04-07 9:06 ` [PATCH 1/2] KVM: x86: remaster kvm_write_tsc code Denis Plotnikov
2017-04-07 9:06 ` [PATCH 2/2] KVM: x86: fix maintaining of kvm_clock stability on guest CPU hotplug Denis Plotnikov
-- strict thread matches above, loose matches on Subject: below --
2017-04-07 9:09 [PATCH v2 0/2] maintaining of kvm_clock stability on guest vCPU hotplug Denis Plotnikov
2017-04-12 19:02 ` 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=1491556007-56332-1-git-send-email-dplotnikov@virtuozzo.com \
--to=dplotnikov@virtuozzo.com \
--cc=den@virtuozzo.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkagan@virtuozzo.com \
--cc=rkrcmar@redhat.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;
as well as URLs for NNTP newsgroup(s).