[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070204125316.GA1945@elf.ucw.cz>
Date: Sun, 4 Feb 2007 13:53:16 +0100
From: Pavel Machek <pavel@....cz>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: paulmck@...ux.vnet.ibm.com, Andrew Morton <akpm@...l.org>,
Ingo Molnar <mingo@...e.hu>, dipankar@...ibm.com,
Gautham Shenoy <ego@...ux.vnet.ibm.com>,
linux-kernel@...r.kernel.org
Subject: Re: Fw: Re: [mm PATCH 4/6] RCU: (now) CPU hotplug
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists