Re: [git pull] RT scheduler updates for tip
From: Ingo Molnar
Date: Fri Dec 12 2008 - 06:34:33 EST
* Gregory Haskins <ghaskins@xxxxxxxxxx> wrote:
> Ingo Molnar wrote:
> > okay, this series is quite bad so i'm disabling it for now. I sent a
> > build fix earlier today, then i triggered this build failure:
> >
> > kernel/built-in.o: In function `dequeue_pushable_task':
> > sched.c:(.text+0x4a9f): undefined reference to `plist_del'
> > kernel/built-in.o: In function `enqueue_pushable_task':
> > sched.c:(.text+0x5734): undefined reference to `plist_del'
> > sched.c:(.text+0x5747): undefined reference to `plist_add'
> >
> > and then this:
> >
> > kernel/sched_rt.c: In function ânext_prioâ:
> > kernel/sched_rt.c:574: error: âstruct rqâ has no member named âcpuâ
> > kernel/sched_rt.c: In function âinc_rt_tasksâ:
> > kernel/sched_rt.c:619: error: ârqâ undeclared (first use in this function)
> > kernel/sched_rt.c:619: error: (Each undeclared identifier is reported only once
> > kernel/sched_rt.c:619: error: for each function it appears in.)
> > kernel/sched_rt.c: In function âdec_rt_tasksâ:
> > kernel/sched_rt.c:667: error: ârqâ undeclared (first use in this function)
> >
> >
> >
>
> Hi Ingo,
> I was able to reproduce your first error (in the previous mail) by
> turning off CONFIG_SMP. I have folded your fix into my series and got
> past it. However, I was not able to reproduce these two new errors. I
> was thinking that perhaps something merged improperly between my
> (older) tip/master and the merge point in cpus4096. So I rebased the
> series on your latest tip/master as of this morning, but it still
> builds fine for me. Could you send me the .config that causes this to
> blow up? I will get it straightened out for you ASAP. Sorry for the
> inconvenience.
Could you send a delta fix against cpus4096 for that bug you fixed?
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/