From: Paul E. McKenney Date: Thu, 15 Aug 2013 17:12:12 +0000 (-0700) Subject: rcu: Distinguish between NOCB and non-NOCB rcu_callback trace events X-Git-Tag: omap-for-v3.13/fixes-for-merge-window-take2~44^2^2~2^2~2 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=756cbf6befe6f59b0b3e0967d92a66c11e2566ed;p=pandora-kernel.git 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: Match operand size per kbuild test robot's advice. ] --- Reading git-diff-tree failed