rcu: Distinguish between NOCB and non-NOCB rcu_callback trace events
authorPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Thu, 15 Aug 2013 17:12:12 +0000 (10:12 -0700)
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Mon, 23 Sep 2013 16:18:14 +0000 (09:18 -0700)
commit756cbf6befe6f59b0b3e0967d92a66c11e2566ed
tree208a54ccf6ed2003fe8020901a6a9515dd5a3273
parent9261dd0da6c6432f08670719069449c6efe4f7a9
rcu: Distinguish between NOCB and non-NOCB rcu_callback trace events

One way to distinguish between NOCB and non-NOCB rcu_callback trace
events is that the former always print zero for the lazy and non-lazy
queue lengths.  Unfortunately, this also means that we cannot see the NOCB
queue lengths.  This commit therefore accesses the NOCB queue lengths,
but negates them.  NOCB rcu_callback trace events should therefore have
negative queue lengths.

Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
[ paulmck: Match operand size per kbuild test robot's advice. ]
kernel/rcutree_plugin.h