kernel/events/core.c

1256  *	    perf_event::child_mutex;
2235 	lockdep_assert_held(&parent_event->child_mutex);
2464  * hold the top-level event's child_mutex, so any descendant that
3217 	mutex_lock(&event->child_mutex);
3234 	mutex_unlock(&event->child_mutex);
5354 	 * Anybody acquiring event->child_mutex after the below loop _must_
5366 	mutex_lock(&event->child_mutex);
5375 		 * Since child_mutex nests inside ctx::mutex, we must jump
5379 		 * child_mutex, the context must also exist and have a !0
5385 		 * Now that we have a ctx ref, we can drop child_mutex, and
5387 		 * can re-acquire child_mutex.
5389 		mutex_unlock(&event->child_mutex);
5391 		mutex_lock(&event->child_mutex);
5394 		 * Now that we hold ctx::mutex and child_mutex, revalidate our
5410 		mutex_unlock(&event->child_mutex);
5415 	mutex_unlock(&event->child_mutex);
5454 	mutex_lock(&event->child_mutex);
5470 	mutex_unlock(&event->child_mutex);
5508 	 *  - parent->child_mutex pins parent->child_list
5583 	mutex_lock(&leader->child_mutex);
5595 	mutex_unlock(&leader->child_mutex);
5603 	mutex_unlock(&leader->child_mutex);
5639 	mutex_lock(&event->child_mutex);
5641 	mutex_unlock(&event->child_mutex);
5741  * Holding the top-level event's child_mutex means that any
5753 	mutex_lock(&event->child_mutex);
5757 	mutex_unlock(&event->child_mutex);
10710 	 * will stop on the parent's child_mutex that our caller is also holding
11919 	mutex_init(&event->child_mutex);
13068 		mutex_lock(&parent_event->child_mutex);
13082 		mutex_unlock(&parent_event->child_mutex);
13202 	mutex_lock(&parent->child_mutex);
13204 	mutex_unlock(&parent->child_mutex);
13354 	mutex_lock(&parent_event->child_mutex);
13357 		mutex_unlock(&parent_event->child_mutex);
13408 	mutex_unlock(&parent_event->child_mutex);