From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: akpm@linux-foundation.org, torvalds@linux-foundation.org,
rjw@sisk.pl, James.Bottomley@SteelEye.com,
aneesh.kumar@gmail.com, drzeus@drzeus.cx, dwmw2@infradead.org,
ego@in.ibm.com, greg@kroah.com, mingo@elte.hu, neilb@suse.de,
oleg@tv-sign.ru, paulmck@linux.vnet.ibm.com, vatsa@in.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: [patch 128/197] freezer: add try_to_freeze calls to all kernel threads
Date: Wed, 09 May 2007 14:06:05 +0200 [thread overview]
Message-ID: <4641B92D.1030909@s5r6.in-berlin.de> (raw)
In-Reply-To: <20070509104949.GA8164@elf.ucw.cz>
Pavel Machek wrote:
>> > Add try_to_freeze() calls to the remaining kernel threads that do not call
>> > try_to_freeze() already, although they set PF_NOFREEZE.
>> >
>> > In the future we are going to replace PF_NOFREEZE with a set of flags that
>> > will be set to indicate in which situations the task should not be frozen (for
>> > example, there can be a task that should be frozen for the CPU hotplugging and
>> > should not be frozen for the system suspend).
[...]
>> Why add no-op-try_to_freeze() everywhere now, instead of adding it later
>> when it will actually be needed? (I.e. "in the future".)
>
> It is needed later in the patch series... for kprobes, etc.
So does freezer_exempt() still do what its name says, or does it
freezer_exempt_but_not_always() now?
--
Stefan Richter
-=====-=-=== -=-= -=--=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2007-05-09 12:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200705090934.l499YTvX019783@shell0.pdx.osdl.net>
2007-05-09 10:44 ` [patch 128/197] freezer: add try_to_freeze calls to all kernel threads Stefan Richter
2007-05-09 10:49 ` Pavel Machek
2007-05-09 12:06 ` Stefan Richter [this message]
2007-05-09 12:16 ` Gautham R Shenoy
2007-05-09 13:20 ` Stefan Richter
2007-05-09 15:29 ` Gautham R Shenoy
2007-05-09 18:18 ` Rafael J. Wysocki
2007-05-09 18:48 ` Stefan Richter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4641B92D.1030909@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@gmail.com \
--cc=drzeus@drzeus.cx \
--cc=dwmw2@infradead.org \
--cc=ego@in.ibm.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=neilb@suse.de \
--cc=oleg@tv-sign.ru \
--cc=paulmck@linux.vnet.ibm.com \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.org \
--cc=vatsa@in.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox