On Tue, Feb 17, 2009 at 07:11:42AM +0100, Damien Wyart wrote:
> * Paul E. McKenney <[email protected]> [2009-02-16 14:39]:
> > What is the easiest way for me to make it easy to trace the return path
> > from __rcu_pending()? Make each return path call an empty function
> > located off where the compiler cannot see it, I guess... Diagnostic
> > patch along these lines below. Frederic, Damien, could you please give
> > it a go? (And of course please let me know if something else is
> > needed.)
>
> As Frederic already sent a trace (made with another method), I'll
> consider for now mine would not be very useful at this stage, so I'm
> waiting for further instructions.
>
> If you need further testing for me, do not hesitate to ask...
I would be very interested to hear whether or not my patch removing
rcu_pending() and rcu_check_callbacks() from the x86_32 idle loop
fixes the problem for you.
Thanx, Paul
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
