From: Pavel Machek <pavel@ucw.cz>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Ken Moffat <zarniwhoop@ntlworld.com>,
Bill Davidsen <davidsen@tmr.com>,
Linux Kernel M/L <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] what should 'uptime' be on suspend?
Date: Wed, 25 Jul 2007 13:59:35 +0000 [thread overview]
Message-ID: <20070725135935.GC9256@ucw.cz> (raw)
In-Reply-To: <20070720104215.476f4cc1.randy.dunlap@oracle.com>
Hi!
> > > I just found a machine which will resume after suspend to memory, using
> > > the mainline kernel (no suspend2 patch).
> > >
> > > On resume I was looking at the uptime output, and it was about six
> > > minutes, FAR longer than the time since resume. So the topic for
> > > discussion is, should the uptime be
> > > - time sine the original boot
> > > - total uptime since first boot, not counting the time suspended
> > > - time since resume
> > > - some other time around six minutes
> > >
> > > Any of the first three could be useful and "right" for some casesm thus
> > > discussion invited.
> > >
> > My ibook has always been able to suspend to RAM. For a long while,
> > uptime was shown as the time since the last boot. At some point,
> > maybe about a year ago, this was "corrected" to show time since boot
> > _less_ time suspended.
> >
> > To be clear, the ibook suspends when I close the lid and resumes
> > when I open it. Uptime used to be convenient, because I could work
> > out when I'd last booted.
>
> man uptime:
> uptime - tell how long the system has been running
>
> I claim that the system is not running when it is suspended,
> so the suspension time should not be included in uptime.
Well. I claim that the system is not running when cpu is in hlt.
...and on some weird machines (openmoko, olpc) they have hardware capable of
suspending most of machine between keypresses. Now, PCs are not there
yet, but sooner or later we will sleep/suspend between keypresses.
It is not worth changing now, but at least runtime suspend should
be accounted as 'running'.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2007-07-25 18:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 2:42 [RFC] what should 'uptime' be on suspend? Bill Davidsen
2007-07-20 17:17 ` Ken Moffat
2007-07-20 17:42 ` Randy Dunlap
2007-07-20 17:57 ` Ken Moffat
2007-07-20 21:49 ` Rafael J. Wysocki
2007-07-21 13:54 ` Bill Davidsen
2007-07-21 16:29 ` Ken Moffat
2007-07-23 15:44 ` Bill Davidsen
2007-07-25 14:02 ` Pavel Machek
2007-07-25 13:59 ` Pavel Machek [this message]
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=20070725135935.GC9256@ucw.cz \
--to=pavel@ucw.cz \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=zarniwhoop@ntlworld.com \
/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.