linux-kernel - Re: A minimally power-aware driver treats all messages as SUSPEND?

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: <200807011617.55501.rjw@sisk.pl>
Date:	Tue, 1 Jul 2008 16:17:54 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Uwe Kleine-König <Uwe.Kleine-Koenig@...i.com>
Cc:	Andrew Morton <akpm@...l.org>,
	David Brownell <dbrownell@...rs.sourceforge.net>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Pavel Machek <pavel@....cz>, linux-kernel@...r.kernel.org
Subject: Re: A minimally power-aware driver treats all messages as SUSPEND?

On Tuesday, 1 of July 2008, Uwe Kleine-König wrote:
> Hello,
> 
> include/linux/pm.h claims:
> 
> 	A minimally power-aware driver treats all messages as SUSPEND
> 	[...].
> 
> This was introduced in commit 82bb67f2 by David Brownell.  At this time
> PM_EVENT_HIBERNATE didn't exist.  This was added in 3a2d5b70 by Rafael
> J. Wysocki without updating the above sentence.  I think a minimally
> power-aware driver should treat all messages as HIBERNATE, shouldn't it?

No, I don't think so.  In the majority of cases, SUSPEND is equivalent to the
combination of FREEZE and HIBERNATE.

Still, this is going to change anyway with the introduction of the new
suspend/hibernation callbacks that are scheduled for 2.6.27.

Thanks,
Rafael
--
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/