trace: events: rcu: Change description of rcu_dyntick trace event (88748e33) · Commits · 戴 / test

The different strings used for describing the polarity are Start, End and StillNonIdle. Since StillIdle is not used in any trace point for rcu_dyntick, it can be removed and StillNonIdle can be added in the description. Because StillNonIdle is used in a few tracepoints for rcu_dyntick. Similarly, USER, IDLE and IRQ are used for describing context in the rcu_dyntick tracepoints. Since, "KERNEL" is not used for any of the rcu_dyntick tracepoints, remove it from the description. Signed-off-by:

Madhuparna Bhowmik <madhuparnabhowmik10@gmail.com> Signed-off-by:

Joel Fernandes (Google) <joel@joelfernandes.org> Signed-off-by:

Paul E. McKenney <paulmck@kernel.org>

include/trace/events/rcu.h

+6 −5

Original line number	Diff line number	Diff line
		@@ -435,11 +435,12 @@ TRACE_EVENT_RCU(rcu_fqs,
		#endif /* #if defined(CONFIG_TREE_RCU) */

		/*
		* Tracepoint for dyntick-idle entry/exit events. These take a string
		* 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.
		* Tracepoint for dyntick-idle entry/exit events. These take 2 strings
		* as argument:
		* polarity: "Start", "End", "StillNonIdle" for entering, exiting or still not
		* being in dyntick-idle mode.
		* context: "USER" or "IDLE" or "IRQ".
		* NMIs nested in IRQs are inferred with dynticks_nesting > 1 in IRQ context.
		*
		* These events also take a pair of numbers, which indicate the nesting
		* depth before and after the event of interest, and a third number that is

Admin message