Lines Matching refs:be

10 thus be used to profile the code that runs on that CPU.
28 The syscall returns the new fd. The fd can be used via the normal
29 VFS system calls: read() can be used to read the counter, fcntl()
30 can be used to set the blocking mode, etc.
32 Multiple counters can be kept open at a time, and the counters
33 can be poll()ed.
52                                 pinned         :  1, /* must always be on PMU */
113 although there may be variations (e.g., different CPUs might count
145 tracer is available, and event_id values can be obtained from
160  * Bits that can be set in hw_event.read_format to request that
180  * Bits that can be set in hw_event.record_type to request information
192 Such (and other) events will be recorded in a ring-buffer, which is
196 or enabled.  If it is initially disabled, it can be enabled by ioctl
205 The 'pinned' bit, if set, specifies that the counter should always be
207 and only to group leaders.  If a pinned counter cannot be put onto the
214 is on the CPU, it should be the only group using the CPU's counters.
222 way to request that counting of events be restricted to times when the
230 operations, these can be used to relate userspace IP addresses to actual
238 counter to be specific to a task:
248 The 'cpu' parameter allows a counter to be made specific to a CPU:
257 gets schedule to. Per task counters can be created by any user, for
263 The 'flags' parameter is currently unused and must be zero.
265 The 'group_fd' parameter allows counter "groups" to be set up.  A
271 considered to be a group with only 1 member.)
274 only be put onto the CPU if all of the counters in the group can be
276 can be meaningfully compared, added, divided (to get ratios), etc.,
285 The mmap size should be 1+2^n pages, where the first page is a meta-data page
290  * Structure of the page that can be mapped via mmap
377          * will be PERF_RECORD_*
412 Counters can be enabled and disabled in two ways: via ioctl and via
416 An individual counter can be enabled with