From mboxrd@z Thu Jan  1 00:00:00 1970
From: Radim =?utf-8?B?S3LEjW3DocWZ?= <rkrcmar@redhat.com>
Subject: Re: [RFC PATCH 2/2] KVM: x86: add support of kvm-clock stablity in L2
Date: Mon, 10 Jul 2017 15:32:16 +0200
Message-ID: <20170710133215.GB28283@potion>
References: <1498647301-130851-1-git-send-email-dplotnikov@virtuozzo.com>
 <1498647301-130851-3-git-send-email-dplotnikov@virtuozzo.com>
 <20170710132526.GA28283@potion>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, den@virtuozzo.com,
        rkagan@virtuozzo.com
To: Denis Plotnikov <dplotnikov@virtuozzo.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:60280 "EHLO mx1.redhat.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S932072AbdGJNcZ (ORCPT <rfc822;kvm@vger.kernel.org>);
        Mon, 10 Jul 2017 09:32:25 -0400
Content-Disposition: inline
In-Reply-To: <20170710132526.GA28283@potion>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

2017-07-10 15:25+0200, Radim Krčmář:
> 2017-06-28 13:55+0300, Denis Plotnikov:
> > Get rid of complex shadow monotonic timekeeper support in KVM.
> > Extend and use timekeeper infrastructure instead.
> > 
> > Make kvm-clock stable in L2 using the changed timekeeper
> 
> I see this patch as two logical changes:
> 
>   1) refactoring that drops host time caching (gtod)
>   2) stable kvmclock for L2 when L1 is using kvmclock
> 
> Doing it in two patches would definitely be nicer and would allow us to
> focus on the (less controversial) L2 enablement.

I just realized that (2) has more complex dependency on (1): we'd need
extra code to get boot_ns from TSC via kvmclock, so deciding the
refactoring first was a good call.