[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m3ac2nt7o8.fsf@zoo.weinigel.se>
Date: 19 Nov 2006 23:04:23 +0100
From: Christer Weinigel <christer@...nigel.se>
To: Linus Torvalds <torvalds@...l.org>
Cc: Chuck Ebbert <76306.1226@...puserve.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...l.org>,
"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: [patch] PM: suspend/resume debugging should depend on SOFTWARE_SUSPEND
Linus Torvalds <torvalds@...l.org> writes:
> I never use SOFTWARE_SUSPEND, and I think the whole concept is totally
> broken.
>
> Sane people use suspend-to-ram, and that's when you need the suspend and
> resume debugging.
>
> Software-suspend is silly. I want my machine back in three seconds, not
> waiting for minutes..
Suspend-to-disk has a few advantages over suspend-to-ram:
With suspend-to-disk I can remove the battery (to put in a fresh
battery when traveling), try doing that with suspend-to-ram. It's
also really useful for my moving my old Thinkpad which has a battery
which is so bad it can't even hold power for suspend-for-ram for more
than a few seconds.
With suspend-to-disk I can suspend Linux, resume Windows to be able to
run that one program I have to run under Windows, suspend Windows and
resume Linux again without having to restart alla applications.
And yes, this have been very useful for me in real life. So it's
really nice to have both suspend-to-disk and suspend-to-ram.
/Christer
--
"Just how much can I get away with and still go to heaven?"
Christer Weinigel <christer@...nigel.se> http://www.weinigel.se
-
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