| 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: Thu, 5 Jul 2007 14:29:06 +0200 From: "Rafael J. Wysocki" <rjw@...k.pl> To: Paul Mackerras <paulus@...ba.org> Cc: Oliver Neukum <oliver@...kum.org>, Miklos Szeredi <miklos@...redi.hu>, mjg59@...f.ucam.org, linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org Subject: Re: [linux-pm] [PATCH] Remove process freezer from suspend to RAM pathway On Thursday, 5 July 2007 02:29, Paul Mackerras wrote: > Rafael J. Wysocki writes: > > > They will not trigger 100% of the time, but sporadically and generally at > > random. > > > > At least the freezer problems are reproducible. ;-) > > Our experience with powermacs has been that it isn't actually all that > hard to get it right for the drivers you care about. Well, I'm a bit suspicious about that. ;-) Namely, if you run your suspend code on one CPU and (do I remeber correctly that?) with kernel preemption disabled, then you practically prevent user land processes from being scheduled when your suspend code is running. If that is the case (of which I'm not sure), the freezer is obviously unnecessary, because you've taken processes out of the equation in a different way ... Greetings, Rafael -- "Premature optimization is the root of all evil." - Donald Knuth - 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