| 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
| ||
|
Date: Tue, 26 May 2009 00:58:53 +0200 From: "Rafael J. Wysocki" <rjw@...k.pl> To: Oliver Neukum <oliver@...kum.org> Cc: nigel@...onice.net, linux-pm@...ts.linux-foundation.org, tuxonice-devel@...ts.tuxonice.net, linux-kernel@...r.kernel.org, Pavel Machek <pavel@....cz> Subject: Re: [TuxOnIce-devel] [RFC] TuxOnIce On Tuesday 26 May 2009, Oliver Neukum wrote: > Am Montag, 25. Mai 2009 23:43:23 schrieb Rafael J. Wysocki: > > > Oh, before I forget to mention and you ask - how to know what allowance > > > for the drivers? I use a sysfs entry - the user then just needs to see > > > what's needed on their first attempt, set up a means of putting that > > > value in the sysfs file in future (eg /etc/hibernate/tuxonice.conf) and > > > then forget about it. > > > > OK, this is reasonable. > > No, I am afraid it is not. The average user has no clue. Even if that > is not the problem, the user never knows for sure he has encountered > the worst case. OK there, but surely it's better to have a sysfs attribute than a fixed value? > If you really have drivers that have exceptionally large memory requirements > (eg. you need to copy video ram), you should tell the system through struct > driver and do accounting at probe and removal of devices. Or perhaps the drivers should allocate memory from a PM notifier (which is called before the freezing of tasks) to avoid the problem? 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/
Powered by blists - more mailing lists