public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	Linux-pm mailing list <linux-pm@lists.osdl.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [RFC] sleepy linux
Date: Sun, 30 Dec 2007 12:15:52 +0100	[thread overview]
Message-ID: <20071230111552.GA8578@elte.hu> (raw)
In-Reply-To: <20071225230731.GA29030@elf.ucw.cz>


* Pavel Machek <pavel@ucw.cz> wrote:

> Todays hardware is mostly capable of doing better: with correctly set 
> up wakeups, machine can sleep and successfully pretend it is not 
> sleeping -- by waking up whenever something interesting happens. Of 
> course, it is easier on machines not connected to the network, and on 
> notebook computers.
> 
> Requirements:
> 
> 0) Working suspend-to-RAM, with kernel being able to bring video back.
> 
> 1) RTC clock that can wake up system

very nice approach! It might require smarter hardware to be really 
efficient, but the generic ability for Linux to utilize S3 automatically 
would _quickly_ drive the creation of smarter hardware i'm sure - so i'd 
propose to include this even if it wastes power in some cases.

a quick feature request: could you please make the wake-on-RTC 
capability generic and add a CONFIG_DEBUG_SUSPEND_ON_RAM=y config option 
(disabled by default) that does a short 1-second suspend-to-RAM sequence 
upon bootup? That way we could test s2ram automatically (which is a MUCH 
needed feature for automated regression testing and automatic 
bisection). In addition, some sort of 'suspend for N seconds' /sys or 
/dev/rtc capability would be nice as well.

btw., how far are you from having a working prototype?

	Ingo

  parent reply	other threads:[~2007-12-30 11:15 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-25 23:07 [RFC] sleepy linux Pavel Machek
2007-12-26 17:28 ` Oliver Neukum
2007-12-26 19:02   ` Pavel Machek
2007-12-26 20:17   ` Pavel Machek
2007-12-26 20:23     ` Oliver Neukum
2007-12-26 20:32       ` Pavel Machek
2007-12-26 23:15         ` Oliver Neukum
2007-12-29 23:48           ` Pavel Machek
2007-12-27  9:41         ` Oliver Neukum
2007-12-29 23:51           ` Pavel Machek
2007-12-30 16:39             ` Oliver Neukum
2007-12-31 14:44               ` Pavel Machek
2008-01-02 10:52                 ` Oliver Neukum
2007-12-26 18:56 ` H. Peter Anvin
2007-12-26 19:00   ` Pavel Machek
2007-12-26 19:22     ` H. Peter Anvin
2007-12-26 20:08   ` Oliver Neukum
2007-12-26 20:43     ` H. Peter Anvin
2007-12-26 20:51       ` Pavel Machek
2007-12-26 20:54         ` H. Peter Anvin
2007-12-29 23:44           ` Pavel Machek
2007-12-26 20:09 ` [linux-pm] " Igor Stoppa
2007-12-30 11:15 ` Ingo Molnar [this message]
2008-01-05 21:51   ` Pavel Machek
2008-01-08 16:37     ` Ingo Molnar
2008-01-08 19:15       ` Pavel Machek

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=20071230111552.GA8578@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox