[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1247151079.12784.10.camel@twins>
Date: Thu, 09 Jul 2009 16:51:19 +0200
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: Matt Mackall <mpm@...enic.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Anton Vorontsov <avorontsov@...mvista.com>,
Andrew Morton <akpm@...ux-foundation.org>, oleg@...hat.com,
mingo@...e.hu, linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH] netpoll: Fix carrier detection for drivers that are
using phylib
On Thu, 2009-07-09 at 09:43 -0500, Matt Mackall wrote:
> Yeah, that's what I had in mind. Probably throw in a define:
>
> /* for disabling scheduling in early boot */
> #define PREEMPT_EARLY (1 + PREEMPT_ACTIVE)
>
> and slap a comment on the sub_preempt_count().
Right, and visit all the other arch init code ;-)
I'll wait to see if Ingo has anything to say about it and then complete
this thing.
> Does anything actually use scheduler_running yet? Perhaps my tree is
> old.
# git grep scheduler_running
kernel/sched.c:static __read_mostly int scheduler_running;
kernel/sched.c: scheduler_running = 1;
kernel/sched_rt.c: if (unlikely(!scheduler_running))
kernel/sched_rt.c: if (unlikely(!scheduler_running))
If memory serves there used to be more, but I think that migrated into
kernel/sched_clock.c, which has sched_clock_running.
> Also, might_sleep's use of system_state probably bears revisiting.
Yeah, all that code is from long before we had scheduler_running (which
was introduced around CFS/.23).
--
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