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 v2 0/2] maintaining of kvm_clock stability on guest vCPU hotplug
Date: Wed, 12 Apr 2017 21:02:26 +0200 [thread overview]
Message-ID: <20170412190225.GD20145@potion> (raw)
In-Reply-To: <1491556193-56543-1-git-send-email-dplotnikov@virtuozzo.com>
2017-04-07 12:09+0300, Denis Plotnikov:
> 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.
Great cleanup as well, applied to kvm/queue, thanks.
next prev parent reply other threads:[~2017-04-12 19:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 9:09 [PATCH v2 0/2] maintaining of kvm_clock stability on guest vCPU hotplug Denis Plotnikov
2017-04-07 9:09 ` [PATCH v2 1/2] KVM: x86: remaster kvm_write_tsc code Denis Plotnikov
2017-04-07 9:09 ` [PATCH v2 2/2] KVM: x86: fix maintaining of kvm_clock stability on guest CPU hotplug Denis Plotnikov
2017-04-12 19:02 ` Radim Krčmář [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-04-07 9:06 [PATCH v2 0/2] maintaining of kvm_clock stability on guest vCPU hotplug 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=20170412190225.GD20145@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.