Lines Matching full:user
2 user_events: User-based Event Tracing
9 User based trace events allow user processes to create events and trace data
18 delete user based events via the u: prefix. The format of the command to
37 Registering within a user process is done via ioctl() out to the
55 User based events show up under tracefs like any other event under the
79 User programs are encouraged to use clearly sized types like u32.
81 **NOTE:** *Long is not supported since size can vary between user and kernel.*
84 This allows user programs to describe custom structs out to tools, if required.
98 Deleting an event from within a user process is done via ioctl() out to the
104 event (in both user and kernel space). User programs should use a separate file
109 When tools attach/record user based events the status of the event is updated
110 in realtime. This allows user programs to only incur the cost of the write() or
113 User programs call mmap() on /sys/kernel/debug/tracing/user_events_status to
121 kernel configurations can change this size to allow more user based events. In
183 If a user enables the user event via ftrace, the output would change to this::
191 **NOTE:** *A status bit of 0 will never be returned. This allows user programs
210 User programs might have well known structs that they wish to use to emit out
222 It's advised for user programs to do the following::