From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
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 13:53:16 +0100 [thread overview]
Message-ID: <20070204125316.GA1945@elf.ucw.cz> (raw)
In-Reply-To: <200702041208.56466.rjw@sisk.pl>
Hi!
> > > > o init/do_mounts_initrd.c line 57 handle_initrd().
> > > > This looks to be short term anyway, so OK to leave.
> > > > But does kernel_execve() clear PF_NOFREEZE?
> > > >
> > > > But it should be OK to freeze the init process when doing CPU
> > > > hotplug ops, right?
> > >
> > > That looks bogus. If it is short term, it can as well live _without_
> > > PF_NOFREEZE. Noone should suspend system at that stage, right?
> >
> > I agree that any attempt to freeze that early in boot would be
> > at best an act of extreme bravery!
>
> 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?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2007-02-04 12:53 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 [this message]
2007-02-04 13:46 ` Rafael J. Wysocki
2007-02-04 13:50 ` Pavel Machek
2007-02-04 13:59 ` Rafael J. Wysocki
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=20070204125316.GA1945@elf.ucw.cz \
--to=pavel@ucw.cz \
--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=rjw@sisk.pl \
/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