The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Gautham R Shenoy <ego@in.ibm.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Pavel Machek <pavel@ucw.cz>,
	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,
	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, 9 May 2007 17:46:41 +0530	[thread overview]
Message-ID: <20070509121641.GA27109@in.ibm.com> (raw)
In-Reply-To: <4641B92D.1030909@s5r6.in-berlin.de>

Hi Stefan, 
On Wed, May 09, 2007 at 02:06:05PM +0200, Stefan Richter wrote:
> 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?

freezer_exempt() as of now does what its name says. I.e, exempt the
thread from all kinds of freeze chills.

But with more subsystems using the process freezer, the exemption needs
to be event specific. There may be threads which should not be frozen 
for say kprobes, should be frozen for cpu-hotplug. This selective
freezing is not yet available. But it will be soon...

> -- 
> Stefan Richter
> -=====-=-=== -=-= -=--=
> http://arcgraph.de/sr/

Regards
gautham.
-- 
Gautham R Shenoy
Linux Technology Center
IBM India.
"Freedom comes with a price tag of responsibility, which is still a bargain,
because Freedom is priceless!"

  reply	other threads:[~2007-05-09 12:17 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
2007-05-09 12:16       ` Gautham R Shenoy [this message]
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=20070509121641.GA27109@in.ibm.com \
    --to=ego@in.ibm.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@gmail.com \
    --cc=drzeus@drzeus.cx \
    --cc=dwmw2@infradead.org \
    --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=stefanr@s5r6.in-berlin.de \
    --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