linux-kernel - Re: [TuxOnIce-devel] [RFC] TuxOnIce

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: <200905261307.22664.oliver@neukum.org>
Date:	Tue, 26 May 2009 13:07:22 +0200
From:	Oliver Neukum <oliver@...kum.org>
To:	Pavel Machek <pavel@....cz>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>, nigel@...onice.net,
	linux-pm@...ts.linux-foundation.org,
	tuxonice-devel@...ts.tuxonice.net, linux-kernel@...r.kernel.org
Subject: Re: [TuxOnIce-devel] [RFC] TuxOnIce

Am Dienstag, 26. Mai 2009 11:19:40 schrieb Pavel Machek:

Hello,

> For small allocations... I still believe we should free a bit of
> memory for s2ram so that small allocations can be done without
> problems.
> 									Pavel

it is essential that this work. Some subsystems, ie. USB, need to allocate
memory to do IO. For them to work, small allocations must be possible.

Now, is this a real issue? Can most devices really save a device state?
This capability seems to me to be limited to memory mapped IO at best.
USB devices generally don't save and restore state but bring the device
into the state it ought to be in, not the state it was in during resumption.

	Regards
		Oliver

--
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/