From mboxrd@z Thu Jan  1 00:00:00 1970
From: Radim =?utf-8?B?S3LEjW3DocWZ?= <rkrcmar@redhat.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
Message-ID: <20170412190225.GD20145@potion>
References: <1491556193-56543-1-git-send-email-dplotnikov@virtuozzo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: pbonzini@redhat.com, mtosatti@redhat.com, kvm@vger.kernel.org,
        rkagan@virtuozzo.com, den@virtuozzo.com
To: Denis Plotnikov <dplotnikov@virtuozzo.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:49344 "EHLO mx1.redhat.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1752506AbdDLTCq (ORCPT <rfc822;kvm@vger.kernel.org>);
        Wed, 12 Apr 2017 15:02:46 -0400
Content-Disposition: inline
In-Reply-To: <1491556193-56543-1-git-send-email-dplotnikov@virtuozzo.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

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.