From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Denis Plotnikov <dplotnikov@virtuozzo.com>
Cc: pbonzini@redhat.com, mtosatti@redhat.com, kvm@vger.kernel.org,
rkagan@virtuozzo.com, den@virtuozzo.com
Subject: Re: [PATCH 0/2] maintaining of kvm_clock stability on guest vCPU hotplug
Date: Wed, 5 Apr 2017 16:23:44 +0200 [thread overview]
Message-ID: <20170405142343.GE6369@potion> (raw)
In-Reply-To: <4c090183-b775-a5f6-a0f2-f8c85a6b1887@virtuozzo.com>
2017-04-05 11:56+0300, Denis Plotnikov:
> ping
Please re-send the series, I don't have it in mailbox and web-archives
don't show it either,
thanks.
> On 23.03.2017 17:28, Denis Plotnikov wrote:
>> 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.
Right, it looks like an incarnation of the deep problem where the kvm
clock with masterclock diverges from host (different frequency), so any
case where the masterclock is synchronized results in time shifts in the
guest.
>>
>> 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 | 59 ++++++++++++++++++------------------------------------
>> 1 file changed, 20 insertions(+), 39 deletions(-)
>>
>
> --
> Best,
> Denis
next prev parent reply other threads:[~2017-04-05 14:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1490279313-254442-1-git-send-email-dplotnikov@virtuozzo.com>
2017-04-05 8:56 ` [PATCH 0/2] maintaining of kvm_clock stability on guest vCPU hotplug Denis Plotnikov
2017-04-05 14:23 ` Radim Krčmář [this message]
2017-04-06 8:08 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=20170405142343.GE6369@potion \
--to=rkrcmar@redhat.com \
--cc=den@virtuozzo.com \
--cc=dplotnikov@virtuozzo.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkagan@virtuozzo.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