xiaomi-sm8450/android_kernel_xiaomi_sm8450
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

rcu: Simplify rcu_eqs_{enter,exit}() non-idle task debug code

Browse Source 
The code that checks for non-idle non-nohz_idle-usermode tasks invoking
rcu_eqs_enter() and rcu_eqs_exit() prints a considerable quantity of
helpful information.  However, these checks fire rarely, so the extra
complexity is no longer worth it.  This commit therefore replaces this
debug code with simple WARN_ON_ONCE() statements.

Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
This commit is contained in:
Paul E. McKenney
2017-10-05 19:55:31 -07:00
parent 9dd238e286
commit e68bbb266d
2 changed files with 7 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
include/trace/events/rcu.h
View File

@@ -424,15 +424,13 @@ TRACE_EVENT(rcu_fqs,
* as argument: "Start" for entering dyntick-idle mode, "Startirq" for
* entering it from irq/NMI, "End" for leaving it, "Endirq" for leaving it
* to irq/NMI, "--=" for events moving towards idle, and "++=" for events
* moving away from idle. "Error on entry: not idle task" and "Error
* on exit: not idle task" indicate that a non-idle task is erroneously
* toying with the idle loop.
* moving away from idle.
*
* These events also take a pair of numbers, which indicate the nesting
* depth before and after the event of interest. Note that task-related
* and interrupt-related events use two separate counters, and that the
* "++=" and "--=" events for irq/NMI will change the counter by two,
* otherwise by one.
* depth before and after the event of interest, and a third number that is
* the ->dynticks counter. Note that task-related and interrupt-related
* events use two separate counters, and that the "++=" and "--=" events
* for irq/NMI will change the counter by two, otherwise by one.
*/
TRACE_EVENT(rcu_dyntick,