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 S1751176AbdKTGbT (ORCPT <rfc822;w@1wt.eu>);
        Mon, 20 Nov 2017 01:31:19 -0500
Received: from la.guarana.org ([173.254.219.205]:39192 "EHLO la.guarana.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1751003AbdKTGbS (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 20 Nov 2017 01:31:18 -0500
X-Greylist: delayed 620 seconds by postgrey-1.27 at vger.kernel.org; Mon, 20 Nov 2017 01:31:18 EST
Date: Mon, 20 Nov 2017 01:20:57 -0500
From: Kevin Easton <kevin@guarana.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
        Mark Salyzyn <salyzyn@android.com>, Petr Mladek <pmladek@suse.com>,
        LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@kernel.org>,
        "H. Peter Anvin" <hpa@zytor.com>,
        Peter Zijlstra <peterz@infradead.org>,
        Andrew Morton <akpm@linux-foundation.org>,
        Prarit Bhargava <prarit@redhat.com>,
        Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
        Steven Rostedt <rostedt@goodmis.org>,
        John Stultz <john.stultz@linaro.org>
Subject: Re: [GIT pull] printk updates for 4.15
Message-ID: <20171120062057.GA31822@la.guarana.org>
References: <7f0e0165-2b22-f2cf-ce6e-8db3d7325973@android.com>
 <CA+55aFxa8gtN54KD48mf7_mNnMdiduhJ5GTKmJmf_VgLkSZ2fQ@mail.gmail.com>
 <alpine.DEB.2.20.1711142341130.2221@nanos>
 <CA+55aFzAvSe9WjSgyUHns+Z3LbpMFWSU_uze0B8XTRzbnk3rVg@mail.gmail.com>
 <e3023e33-149a-e741-b937-1244797ef9c2@android.com>
 <CA+55aFz44J+fs72JckP_F_DvFJnb1kJ72OAvFj+e-+gCtS9RQA@mail.gmail.com>
 <alpine.DEB.2.20.1711160011300.2146@nanos>
 <CA+55aFytxdwLTQYKWsUJDbrEUYEQr7dzH9NoaKAF-LDnyb2_sA@mail.gmail.com>
 <alpine.DEB.2.20.1711160804350.2265@nanos>
 <alpine.DEB.2.20.1711180123360.2186@nanos>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.20.1711180123360.2186@nanos>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Sat, Nov 18, 2017 at 01:26:07AM +0100, Thomas Gleixner wrote:
> On Thu, 16 Nov 2017, Thomas Gleixner wrote:
> > I hope that I can find a few spare cycles to whip up a POC patch which does
> > not make stuff fall apart immediately.
> 
> Here you go. It survived suspend resume in a VM.
> 
> Thanks,
> 
> 	tglx
> 
> 8<------------------------
> Subject: timekeeping: Make monotonic behave like boottime
> From: Thomas Gleixner <tglx@linutronix.de>
> Date: Fri, 17 Nov 2017 11:46:48 +0100
> 
> Clock MONOTONIC is not fast forwarded by the time spent in suspend on
> resume. This is only done for BOOTTIME.
> 
> It would be desired to get rid of that difference, but the difference
> between clock MONOTONIC and clock BOOTTIME is well documented so there
> might be applications which depend on that behaviour.

As a comment from the userspace peanut gallery, I personally hope this
does pass muster.  The existing POSIX wording implies that MONOTONIC
doesn't stop counting over suspend, and that's what you need when you
want to know the time elapsed between two external events.

    - Kevin
>