From: Gautham R Shenoy <ego@in.ibm.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Oleg Nesterov <oleg@tv-sign.ru>,
Pavel Machek <pavel@ucw.cz>,
Pekka Enberg <penberg@cs.helsinki.fi>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -mm 2/2] Introduce freezer flags
Date: Fri, 27 Apr 2007 22:03:47 +0530 [thread overview]
Message-ID: <20070427163347.GD22639@in.ibm.com> (raw)
In-Reply-To: <20070427161940.GB1046@uranus.ravnborg.org>
On Fri, Apr 27, 2007 at 06:19:40PM +0200, Sam Ravnborg wrote:
> On Fri, Apr 27, 2007 at 05:40:16PM +0200, Rafael J. Wysocki wrote:
>
> > --- linux-2.6.21-rc7-mm2.orig/kernel/fork.c
> > +++ linux-2.6.21-rc7-mm2/kernel/fork.c
> > @@ -921,11 +921,14 @@ static inline void copy_flags(unsigned l
> > {
> > unsigned long new_flags = p->flags;
> >
> > - new_flags &= ~(PF_SUPERPRIV | PF_NOFREEZE);
> > + new_flags &= ~PF_SUPERPRIV;
> > new_flags |= PF_FORKNOEXEC;
> > if (!(clone_flags & CLONE_PTRACE))
> > p->ptrace = 0;
> > p->flags = new_flags;
> > +#ifdef CONFIG_FREEZER
> > + p->freezer_flags = 0;
> > +#endif
> > }
> Could we have a dedicated clear_freeze_flag() so we could drop the ifdef?
>
> > + clear_freeze_flag(p);
That means something else. clear_freeze_flag() just clears the
TFF_FREEZE flag and not necessarily everything.
Besides, this is the only place where we would need to clear all the bits
of p->freezer_flags. Not sure if having a static inline helper function
is worth it.
>
> Or maybe we have it already?
We don't yet. But can if badly needed :-)
>
>
> Sam
Thanks and 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!"
next prev parent reply other threads:[~2007-04-27 16:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 15:37 [PATCH -mm 0/2] Separate freezer from PM code Rafael J. Wysocki
2007-04-27 15:38 ` [PATCH -mm 1/2] " Rafael J. Wysocki
2007-04-27 16:15 ` Sam Ravnborg
2007-04-27 16:25 ` Jeremy Fitzhardinge
2007-04-27 20:20 ` Rafael J. Wysocki
2007-04-27 20:20 ` Jeremy Fitzhardinge
2007-04-27 21:29 ` Rafael J. Wysocki
2007-04-29 8:43 ` Sam Ravnborg
2007-04-27 15:40 ` [PATCH -mm 2/2] Introduce freezer flags Rafael J. Wysocki
2007-04-27 16:19 ` Sam Ravnborg
2007-04-27 16:33 ` Gautham R Shenoy [this message]
2007-04-27 21:40 ` Gautham R Shenoy
2007-04-27 21:49 ` Rafael J. Wysocki
2007-04-27 21:49 ` Gautham R Shenoy
2007-04-27 22:09 ` Rafael J. Wysocki
2007-04-27 22:07 ` Pavel Machek
2007-04-27 22:56 ` Rafael J. Wysocki
2007-04-28 7:07 ` Pavel Machek
2007-04-28 1:34 ` [PATCH -mm] Allow selective freezing of the system for different events Gautham R Shenoy
2007-04-28 6:22 ` Andrew Morton
2007-04-28 7:45 ` Gautham R Shenoy
2007-04-29 17:51 ` Rafael J. Wysocki
2007-04-30 19:19 ` Gautham R Shenoy
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=20070427163347.GD22639@in.ibm.com \
--to=ego@in.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@tv-sign.ru \
--cc=pavel@ucw.cz \
--cc=penberg@cs.helsinki.fi \
--cc=rjw@sisk.pl \
--cc=sam@ravnborg.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.