Steven Rostedt (VMware) 1c347a94ca tracing: Comment why cond_snapshot is checked outside of max_lock protection
Before setting tr->cond_snapshot, it must be NULL before it can be updated.
It can go to NULL when a trace event hist trigger is created or removed, and
can only be modified under the max_lock spin lock. But because it can only
be set to something other than NULL under both the max_lock spin lock as
well as the trace_types_lock, we can perform the check if it is not NULL
only under the trace_types_lock and fail out without having to grab the
max_lock spin lock.

This is very subtle, and deserves a comment.

Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
2019-02-20 13:51:08 -05:00
..
2018-11-26 18:41:21 -05:00
2018-11-26 18:41:21 -05:00
2018-12-19 13:52:44 -05:00
2019-01-21 11:15:38 +01:00
2018-12-28 12:42:30 -08:00
2018-10-31 08:54:16 -07:00
2019-01-15 09:43:12 -08:00
2018-07-03 09:20:44 +02:00
2019-01-11 18:05:40 -08:00
2019-02-01 15:46:23 -08:00