| 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
| ||
|
Message-ID: <20070218125610.GA16349@elf.ucw.cz> Date: Sun, 18 Feb 2007 13:56:10 +0100 From: Pavel Machek <pavel@....cz> To: "Rafael J. Wysocki" <rjw@...k.pl> Cc: ego@...ibm.com, akpm@...l.org, paulmck@...ibm.com, mingo@...e.hu, vatsa@...ibm.com, dipankar@...ibm.com, venkatesh.pallipadi@...el.com, linux-kernel@...r.kernel.org, oleg@...sign.ru Subject: Re: [RFC PATCH(Experimental) 0/4] Freezer based Cpu-hotplug Hi! > > > So I think tonight I'll start adding try_to_freeze() to the kernel threads that > > > set PF_NOFREEZE. > > > > cool! While you are at it, let me try to enhance the freezer api's > > to incorporate the PFE_* flags. > > Here's a patch that adds try_to_freeze() to all kernel threads that didn't call > it before. It shouldn't change the behavior of the threads in question, since > they won't be frozen because the are flagged as PF_NOFREEZE (of course > we are going to change this later). Looks ok. > Compile-tested on x86_64 with allmodconfig. > > Pavel, do you think we can remove the PF_NOFREEZE from bluetooth, > BTW? Yes... bluetooth has no reason to play with NOFREEZE. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html - 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