From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Rob Landley <rob@landley.net>,
linux-kernel@vger.kernel.org,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: Question about /proc/uptime
Date: Mon, 30 Dec 2013 16:26:17 +0100 [thread overview]
Message-ID: <20131230162617.1b013251@mschwide> (raw)
In-Reply-To: <20131230151110.GA29636@redhat.com>
On Mon, 30 Dec 2013 16:11:10 +0100
Oleg Nesterov <oleg@redhat.com> wrote:
> On 12/30, Martin Schwidefsky wrote:
> <
> > On Fri, 27 Dec 2013 15:45:04 +0100
> > Oleg Nesterov <oleg@redhat.com> wrote:
> >
> > > Add Frederic, I am not sure I understand this correctly.
> > >
> > > On 12/25, Rob Landley wrote:
> > > >
> > > > There are two values here, the first is seconds since boot time (which
> > > > is just elapsed time; at one point it was ajusted for suspend and that
> > > > was revered as confusing).
> > >
> > > Hmm, uptime_proc_show() still uses get_monotonic_boottime(), this should
> > > include suspend time?
> >
> > The first value of /proc/uptime is the amount of time the system has been
> > running, the sum of the suspend time is not included.
>
> Hmm. It uses get_monotonic_boottime() and this helper adds
> timekeeper->total_sleep_time to the returned value? Even the comment says
>
> * This is similar to CLOCK_MONTONIC/ktime_get_ts, but also
> * includes the time spent in suspend.
>
> > timekeeping_resume()
> > is supposed to take care of that.
>
> 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.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2013-12-30 15:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-26 2:30 Question about /proc/uptime Rob Landley
2013-12-27 14:45 ` Oleg Nesterov
2013-12-30 8:56 ` Martin Schwidefsky
2013-12-30 15:11 ` Oleg Nesterov
2013-12-30 15:26 ` Martin Schwidefsky [this message]
2014-01-01 4:17 ` Rob Landley
2014-01-01 12:41 ` Martin Schwidefsky
2014-01-01 21:21 ` Rob Landley
2014-01-02 8:28 ` Martin Schwidefsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131230162617.1b013251@mschwide \
--to=schwidefsky@de.ibm.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=rob@landley.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.