* Ingo Molnar <[EMAIL PROTECTED]> wrote:
* Ingo Molnar <[EMAIL PROTECTED]> wrote:
hm, another thing: i think call_rcu() needs to take the read-lock. Right now it assumes that it has the data structure private, but that's only statistically true on PREEMPT_RT: another CPU may have this CPU's RCU control structure in use. So IRQs-off (or preempt-off) is not a guarantee to have the data structure, the read lock has to be taken.
i've reworked the code to use the read-lock to access the per-CPU data RCU structures, and it boots with 2 CPUs and PREEMPT_RT now. The -40-05 patch can be downloaded from the usual place:
bah, it's leaking dentries at a massive scale. I'm giving up on this variant for the time being and have gone towards a much simpler variant, implemented in the -40-07 patch at:
http://redhat.com/~mingo/realtime-preempt/
Actually this is more correctly related to -RT-2.6.12-rc1-V0.7.41-08. This one boots on one of my SMP systems (dual 2.6 GHz Zeon) doesn't on the other (dual PIII 933 MHz). Unfortunately not close to the one that doesn't boot right now so can't debug it at all.
Was still building on the UP box, but now that one seems to have gone down in flames. This system was running -RT-2.6.12-rc1-V0.7.41-00 while trying to build -RT-2.6.12-rc1-V0.7.41-07. :(
-- kr - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
