From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: paulmck@linux.vnet.ibm.com, Andrew Morton <akpm@osdl.org>,
Ingo Molnar <mingo@elte.hu>,
dipankar@in.ibm.com, Gautham Shenoy <ego@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: Fw: Re: [mm PATCH 4/6] RCU: (now) CPU hotplug
Date: Sun, 4 Feb 2007 14:59:48 +0100 [thread overview]
Message-ID: <200702041459.49562.rjw@sisk.pl> (raw)
In-Reply-To: <20070204135049.GC1945@elf.ucw.cz>
On Sunday, 4 February 2007 14:50, Pavel Machek wrote:
> Hi!
>
> > > > This is needed so that the _resume_ works, when it's handled from the user land
> > > > by our resume tool. Currently, the resume code calls
> > > > freeze_processes() too.
> > >
> > > I do not understand... freeze_processes() always leaves curent process
> > > running... why is it needed?
> >
> > IIRC, the do_linuxrc thread cannot be frozen (doesn't call try_to_freeze()),
> > so the freeze_processes() during the resume fails and the resume fails as a
> > result.
>
> Aha, ok. (We still may want to add try_to_freeze there; there's no
> reason to have that running while resuming).
>
> > Still, I have an idea:
> >
> > Instead of hunting for PF_NOFREEZE and wondering if the suspend/resume fails
> > when we remove them or replace them with try_to_freeze(), why don't we add
> > an "ignore_pf_nofreeze" argument to freeze_processes() and make it regard
> > _all_ tasks as if they haven't set PF_NOFREEZE when this "ignore_pf_nofreeze"
> > is set? Of course, additionally we'll have to make everyone call
> > try_to_freeze(), even if they set PF_NOFREEZE anyway.
> >
> > Then, if freeze_processes() is called with "ignore_pf_nofreeze = 0", it will
> > work just as it does now. However, if it's called with
> > "ignore_pf_nofreeze = 1", it will try to make all prcesses enter the
> > refrigerator. The "ignore_pf_nofreeze = 0" version will be suitable for us
> > (ie. suspend etc.) and the "ignore_pf_nofreeze = 1" version will be suitable
> > for the CPU hotplug and such things.
>
> Yep, something like that will be needed. Probably more finegrained
> (with flags), because CPU hotplug and kprobes may want their own sets
> of unfreezeable processes.
Yes, but for this purpose we'll need to use one more task flag at least, I
think. Or transform PF_NOFREEZE into a 2-bit field with values from 0 to 3
indicating the "freezing level" at which given task should be frozen and
call freeze_processes() with the level as an argument?
Paul, what is your opnion?
Rafael
next prev parent reply other threads:[~2007-02-04 13:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070124011519.GG1613@linux.vnet.ibm.com>
[not found] ` <20070124090111.GC27221@in.ibm.com>
[not found] ` <20070124161559.GA1762@linux.vnet.ibm.com>
[not found] ` <20070124210645.GA19650@in.ibm.com>
2007-01-26 19:11 ` Dipankar Sarma
2007-01-26 19:28 ` Andrew Morton
2007-01-26 19:46 ` Dipankar Sarma
2007-01-26 20:17 ` Andrew Morton
2007-01-26 20:44 ` Dipankar Sarma
2007-01-26 21:29 ` Andrew Morton
2007-01-28 22:47 ` Paul E. McKenney
2007-01-28 23:30 ` Andrew Morton
2007-01-29 2:40 ` Paul E. McKenney
2007-01-29 19:12 ` Ingo Molnar
2007-01-30 2:45 ` Paul E. McKenney
2007-01-30 7:33 ` Ingo Molnar
2007-01-30 16:02 ` Paul E. McKenney
2007-01-30 16:44 ` Rafael J. Wysocki
2007-01-30 18:27 ` Andrew Morton
2007-01-30 19:49 ` Paul E. McKenney
2007-01-31 23:10 ` Paul E. McKenney
2007-02-03 0:17 ` Pavel Machek
2007-02-04 4:39 ` Paul E. McKenney
2007-02-04 11:08 ` Rafael J. Wysocki
2007-02-04 12:53 ` Pavel Machek
2007-02-04 13:46 ` Rafael J. Wysocki
2007-02-04 13:50 ` Pavel Machek
2007-02-04 13:59 ` Rafael J. Wysocki [this message]
2007-02-03 0:01 ` Pavel Machek
2007-02-03 22:27 ` Rafael J. Wysocki
2007-02-04 0:31 ` Paul E. McKenney
2007-01-30 14:02 ` Gautham R Shenoy
2007-01-30 16:47 ` Paul E. McKenney
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=200702041459.49562.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@osdl.org \
--cc=dipankar@in.ibm.com \
--cc=ego@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=pavel@ucw.cz \
/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
Powered by JetHome