Lines Matching +full:ftrace +full:- +full:size

2 user_events: User-based Event Tracing
8 --------
10 that can be viewed via existing tools, such as ftrace and perf.
22 tools that can read trace_events (such as ftrace and perf). The registration
24 the status bit. This describes which bit in little-endian format in the
36 -----------
44         u32 size;
50 The struct user_reg requires two inputs, the first is the size of the structure
58 or perf record -e user_events:[name] when attaching/recording.
76   type name [size]
81 **NOTE:** *Long is not supported since size can vary between user and kernel.*
83 The size is only valid for types that start with a struct prefix.
97 -----------
108 ------
116 is always in little-endian format. Programs can check if the bit is set either
117 using a byte-wise index with a mask or a long-wise index with a little-endian
120 Currently the size of user_events_status is a single page, however, custom
121 kernel configurations can change this size to allow more user based events. In
122 all cases the size of the file is a multiple of a page size.
128 A byte-wise index check is performed as follows::
142 A long-wise index check is performed as follows::
183 If a user enables the user event via ftrace, the output would change to this::
185   1:test # Used by ftrace
195 ------------
201 payload of the event. Then the data would have to be 8 bytes (2 ints) in size,
237 ------------