linux-kernel - Re: [RFC][PATCH -mm 2/3] freezer: Introduce freezer

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: <a781481a0704222018o65f34f79gb1ffe521b83d481f@mail.gmail.com>
Date:	Mon, 23 Apr 2007 08:48:04 +0530
From:	"Satyam Sharma" <satyam.sharma@...il.com>
To:	"Paul Jackson" <pj@....com>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>, akpm@...ux-foundation.org,
	mingo@...e.hu, ego@...ibm.com, oleg@...sign.ru,
	linux-kernel@...r.kernel.org, vatsa@...ibm.com, paulmck@...ibm.com,
	pavel@....cz
Subject: Re: [RFC][PATCH -mm 2/3] freezer: Introduce freezer_flags

On 4/23/07, Paul Jackson <pj@....com> wrote:
> One more question - why would I want to do this?

Check out the FAQ in Documentation/power/swsusp.txt.

> Is this like something that would be useful on a laptop, to suspend
> activity and reduce battery drain, while preserving the current state
> of ones sessions and avoiding having to logout or shutdown?

Yes, the original purpose for the inclusion of the freezer code was to
support suspend-resume (mainly for laptops, but suspend-resume could
be useful in other circumstances too, see the FAQ).

> Is it useful for quietting a system down before doing hot plug or
> unplug of key components, such as processors and memory?

Yes, the freezer is (proposed to be, at least) moving on from being
merely a suspend-resume-only thing to other usage scenarios, such as
kprobes and hotlpug.
-
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/