From mboxrd@z Thu Jan 1 00:00:00 1970 From: Denis Plotnikov Subject: Re: [RFC PATCH 2/2] KVM: x86: add support of kvm-clock stablity in L2 Date: Fri, 21 Jul 2017 17:01:23 +0300 Message-ID: <68aae01f-2062-bc53-0a03-13c1eb80f54f@virtuozzo.com> References: <1498647301-130851-1-git-send-email-dplotnikov@virtuozzo.com> <1498647301-130851-3-git-send-email-dplotnikov@virtuozzo.com> <20170710132526.GA28283@potion> <20170710133215.GB28283@potion> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Cc: kvm@vger.kernel.org, pbonzini@redhat.com, den@virtuozzo.com, rkagan@virtuozzo.com To: =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= Return-path: Received: from mail-db5eur01on0106.outbound.protection.outlook.com ([104.47.2.106]:16000 "EHLO EUR01-DB5-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751996AbdGUOBk (ORCPT ); Fri, 21 Jul 2017 10:01:40 -0400 In-Reply-To: <20170710133215.GB28283@potion> Content-Language: en-US Sender: kvm-owner@vger.kernel.org List-ID: On 10.07.2017 16:32, Radim Krčmář wrote: > 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. > I agree and will return with the set of patches shortly. Thanks for reviewing! -- Best, Denis