lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070725135935.GC9256@ucw.cz>
Date:	Wed, 25 Jul 2007 13:59:35 +0000
From:	Pavel Machek <pavel@....cz>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	Ken Moffat <zarniwhoop@...world.com>,
	Bill Davidsen <davidsen@....com>,
	Linux Kernel M/L <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] what should 'uptime' be on suspend?

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ