Date: Wed, 1 Jan 2014 13:41:21 +0100
From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Rob Landley <rob@landley.net>
Cc: Oleg Nesterov <oleg@redhat.com>, linux-kernel@vger.kernel.org,
        Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: Question about /proc/uptime
Message-ID: <20140101134121.79787caf@mschwide>
In-Reply-To: <52C396E3.5080000@landley.net>
References: <1388025009.1176.17@driftwood>
	<20131227144504.GA17192@redhat.com>
	<20131230095656.4c78dd98@mschwide>
	<20131230151110.GA29636@redhat.com>
	<20131230162617.1b013251@mschwide>
	<52C396E3.5080000@landley.net>
Organization: IBM Corporation
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1005
Lines: 29

On Tue, 31 Dec 2013 22:17:39 -0600
Rob Landley <rob@landley.net> wrote:

> On 12/30/13 09:26, Martin Schwidefsky wrote:
> > On Mon, 30 Dec 2013 16:11:10 +0100
> > Oleg Nesterov <oleg@redhat.com> wrote:
> >> Not sure I understand... except that timekeeping_resume() does
> >> __timekeeping_inject_sleeptime().
> >
> > Hmm, you are right. The sleeptime is added to the monotonic boottime.
> > So the first value of /proc/uptime is the wall-time since boot.
> > And the second value is combined idle time over all cpus.
> 
> Is there an obvious way to query the non-suspend uptime from userspace?

clock_gettime with CLOCK_MONOTONIC gives you the uptime minus without the
suspend time.

-- 
blue skies,
   Martin.

"Reality continues to ruin my life." - Calvin.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/