Paul,
I ran your original preemption test of RCU torture, and after several
minutes, my preempt boost patch had one Preemption stall. I then
disabled preemption boosting, and ran the preempt torture again, and it
seemed to never stall. Something seemed strange, so I took a look.
Looks like you
--
On Wed, 3 Oct 2007, Clark Williams wrote:
> >
> > I could put a hack in that fixes the issue when detected, and still prints
> > out a warning. I'll do that for now, until we find the problem area. I
> > think the first warning probably had the want that corrupted us, and then
> > we got floo
** RFC not for inclusion **
Although this patch is against the -rt tree, it is also applicable to
mainline after Paul's RCU preempt patches make it in.
This patch adds RCU preemption boosting to RCU readers that were
preempted (or sleep due to spin_locks in -rt).
The approach I took is similar t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steven Rostedt wrote:
>
> grmbl grmbl!!!
>
> We are missing a match somewhere. Most likely in the suspend or resume
> code. It's expected that if a CPU is idle with no ticks then the
> dynticks_progress_counter is even, otherwise it is odd. This che
