Re: [patch] voluntary-preempt-2.6.9-rc2-mm1-S1

[K.R. Foley]

Ingo Molnar wrote:
> i've released the -S1 VP patch:
>
>   http://redhat.com/~mingo/voluntary-preempt/voluntary-preempt-2.6.9-rc2-mm1-S1
>
> NOTE: this patch is against Andrew's -mm tree and the VP patchset will
> stay based on -mm until the merging process has been finished.
>
> to get a 2.6.9-rc2-mm1-VP-S1 kernel, the patching order is:
>
>    http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.8.tar.bz2
>  + http://kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.9-rc2.bz2
>  + http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.9-rc2/2.6.9-rc2-mm1/2.6.9-rc2-mm1.bz2
>  + http://redhat.com/~mingo/voluntary-preempt/voluntary-preempt-2.6.9-rc2-mm1-S1
>
> Changes relative to -S0:
>
> - lots of merging. A good chunk of the VP patch latency breakers and
>   support patches are in -mm already.
>
> - integrated my 'preemptible big kernel lock' patch into VP. This makes 
>   all BKL code preemptible while keeping correctness. A new debugging 
>   infrastructure has been added to catch code that might use the BKL
>   in an unsafe way. If the debugging check triggers it will print 
>   messages like:
>
>     using smp_processor_id() in preemptible code: bash/1020
>
>   please report such messages and backtraces to me. Most of the messages 
>   i've fixed so far were false positives, but one bug has been caught 
>   already via this.
>
>   Also, this BKL patch allowed the removal of two questionable 
>   latency breakers: the tty.c and the DRM BKL relaxation hack.
>
> - fixed an SMP hardirq redirection bug - IRQ threads could be bound to 
>   multiple CPUs resulting in potentially illegal preemption of hardirq
>   contexts.
>
> - temporarily dropped the ppc/ppc64 GENERIC_HARDIRQS changes, they broke
>   and i cannot test them.
>
> Reports, comments welcome,
>
> 	Ingo
> -

Is anyone else having trouble getting this to build on x86 smp? I am 
getting undefined references to smp_processor_id within most, if not 
all, modules.

kr
-
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/