I too am having "issues" with linux spinlocks... but in a massively
parrallel situation. It appears that something isn't working right and I
don't think it's _my_ code. ;) I was wondering what the incentive is for
moving code to a different section (besides that it totally confuses my
debugger! :)... Why not just leave it inline? Trying to make fall
through happen?
Okay, my comment is that there is a lot of errata on the pentium line (and
others I'm sure) with reguards to caching and the lock prefix. Have you
tried just adding a lock prefix to the spin_unlock "movb" instruction?
-Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/