3.0 and RCU: what went wrong
3.0 and RCU: what went wrong
Posted Jul 30, 2011 3:45 UTC (Sat) by pr1268 (guest, #24648)Parent article: 3.0 and RCU: what went wrong
I'm curious, in static void rcu_read_unlock_special(struct task_struct *t), on line 5 unsigned long flags is declared but uninitialized. Later, on line 11, it is passed-by-value to another function. Is there some missing code not shown that initializes flags?
Thank you for the neat article—I openly admit that a lot of it is hard for me to follow, but then I'm not as fluent in low-level kernel internals as Paul is. (And, I'm incredibly happy to know that people as knowledgeable as Paul are running the Linux Kernel Show™. ;-)
Posted Jul 30, 2011 5:19 UTC (Sat)
by cladisch (✭ supporter ✭, #50193)
[Link]
Not using a pointer is a little bit more efficient when accessing it from inline assembler.
3.0 and RCU: what went wrong