[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1247055145.9777.52.camel@twins>
Date: Wed, 08 Jul 2009 14:12:25 +0200
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: avorontsov@...mvista.com
Cc: Oleg Nesterov <oleg@...hat.com>, Ingo Molnar <mingo@...e.hu>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH/RFC] sched: Remove SYSTEM_RUNNING checks from
cond_resched*()
On Wed, 2009-07-08 at 16:03 +0400, Anton Vorontsov wrote:
> On Wed, Jul 08, 2009 at 08:24:23AM +0200, Peter Zijlstra wrote:
> > On Wed, 2009-07-08 at 02:50 +0200, Oleg Nesterov wrote:
> >
> > > /*
> > > * It is valid to assume CPU-locality during early bootup:
> > > */
> > > if (system_state != SYSTEM_RUNNING)
> > > goto out;
> > >
> > > this doesn't look right, smp_init() is called before we set
> > > SYSTEM_RUNNING.
> >
> > The thing is, there's also ton's of code that might end up calling
> > cond_resched() and co before the scheduler is fully initialized.
>
> Hm. Speaking of cond_resched*() only, then it should be pretty
> safe to convert the SYSTEM_RUNNING checks to scheduler_running,
> no? scheduler_running is set after sched_init().
Hmm, that might work, I'd have to audit sched_init_smp() as it seems to
do way too much...
--
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