Function report

Linux Kernel

v5.5.9

Brick Technologies Co., Ltd

Source Code:kernel\events\core.c Create Date:2022-07-28 13:34:45
Last Modify:2022-05-20 07:50:19 Copyright©Brick
home page Tree
Annotation kernel can get tool activityDownload SCCTChinese

Name:Remove user event from the owner task.

Proto:static void perf_remove_from_owner(struct perf_event *event)

Type:void

Parameter:

TypeParameterName
struct perf_event *event
4661  _read_lock() - mark the beginning of an RCU read-side critical section* When synchronize_rcu() is invoked on one CPU while other CPUs* are within RCU read-side critical sections, then the* synchronize_rcu() is guaranteed to block until after all the other
4668  owner = READ_ONCE(owner)
4669  If owner Then
4675  get_task_struct(owner)
4677  _read_unlock() - marks the end of an RCU read-side critical section.* In most situations, rcu_read_unlock() is immune from deadlock.* However, in kernels built with CONFIG_RCU_BOOST, rcu_read_unlock()
4679  If owner Then
4688  mutex_lock_nested( & perf_event_mutex, For trivial one-depth nesting of a lock-class, the following* global define can be used. (Subsystems with multiple levels* of nesting should define their own lock-nesting subclasses.))
4696  If owner Then
4697  list_del_init - deletes entry from list and reinitialize it.*@entry: the element to delete from the list.
4698  smp_store_release( & owner, NULL)
4700  mutex_unlock - release the mutex*@lock: the mutex to be released* Unlock a mutex that has been locked by this task previously.* This function must not be used in interrupt context. Unlocking* of a not locked mutex is not allowed.
4701  put_task_struct(owner)
Caller
NameDescribe
perf_event_release_kernelKill an event dead; while event:refcount will preserve the event* object, it will not preserve its functionality. Once the last 'user'* gives up the object, we'll destroy the thing.