From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1753592AbdLHLXU (ORCPT <rfc822;w@1wt.eu>);
        Fri, 8 Dec 2017 06:23:20 -0500
Received: from mx2.suse.de ([195.135.220.15]:53523 "EHLO mx2.suse.de"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1753437AbdLHLXP (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 8 Dec 2017 06:23:15 -0500
Date: Fri, 8 Dec 2017 12:23:12 +0100
From: Petr Mladek <pmladek@suse.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Prarit Bhargava <prarit@redhat.com>,
        LKML <linux-kernel@vger.kernel.org>,
        Linus Torvalds <torvalds@linuxfoundation.org>,
        Mark Salyzyn <salyzyn@android.com>, Ingo Molnar <mingo@kernel.org>,
        "H. Peter Anvin" <hpa@zytor.com>,
        Peter Zijlstra <peterz@infradead.org>,
        Andrew Morton <akpm@linux-foundation.org>,
        Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
        Steven Rostedt <rostedt@goodmis.org>, Joe Perches <joe@perches.com>
Subject: Re: [RFC patch 7/7] timekeeping: Hack to use fine grained timestamps
 during boot
Message-ID: <20171208112312.GB3148@linux.suse>
References: <20171115181531.322572387@linutronix.de>
 <20171115182657.703928462@linutronix.de>
 <20171123125823.gnhwtnx6bxd3tb4q@pathway.suse.cz>
 <205229e2-fab4-31cb-60cd-f36bc2228804@redhat.com>
 <alpine.DEB.2.20.1711281946140.2222@nanos>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.20.1711281946140.2222@nanos>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue 2017-11-28 19:47:09, Thomas Gleixner wrote:
> On Tue, 28 Nov 2017, Prarit Bhargava wrote:
> > On 11/23/2017 07:58 AM, Petr Mladek wrote:
> > > On Wed 2017-11-15 19:15:38, Thomas Gleixner wrote:
> > >> For demonstration purposes only.
> > >>
> > >> Add a disgusting hack to work around the fact that high resolution clock
> > >> MONOTONIC accessors are not available during early boot and return stale
> > >> time stamps accross suspend/resume when the current clocksource is not
> > >> flagged with CLOCK_SOURCE_SUSPEND_ACCESS_OK.
> > >>
> > >> Use local_clock() to provide timestamps in early boot and when the
> > >> clocksource is not accessible after timekeeping_suspend(). In the
> > >> suspend/resume case this might cause non monotonic timestamps.
> > > 
> > > I get the non-monotonic times even during boot:
> > > 
> > > [    0.026709] smp: Bringing up secondary CPUs ...
> > > [    0.027973] x86: Booting SMP configuration:
> > > [    0.028006] .... node  #0, CPUs:      #1
> > > [    0.004000] kvm-clock: cpu 1, msr 1:3ff51041, secondary cpu clock
> > >      ^^^^^^^^
> 
> Which is interesting as this should happen even w/o those patches. 

Good point. I really see this even without those patches.

I was confused because I saw the following with this patchset
but without this latest patch:

[    0.016000] smp: Bringing up secondary CPUs ...
[    0.016000] x86: Booting SMP configuration:
[    0.020000] .... node  #0, CPUs:      #1
[    0.020000] kvm-clock: cpu 1, msr 1:3ff52041, secondary cpu clock
[    0.024000] KVM setup async PF for cpu 1
[    0.024000] kvm-stealtime: cpu 1, msr 13fc8d940

It is monotonic. The only drawback is that the resolution of the
monotonic clock is low at this stage.

Best Regards,
Petr