Lines Matching refs:to

10 thus be used to profile the code that runs on that CPU.
29 VFS system calls: read() can be used to read the counter, fcntl()
30 can be used to set the blocking mode, etc.
115 If a CPU is not able to count the selected event, then the system call
119 and accessed as raw events.  For example, to count "External bus
121 in a 0x4064 event_id value and set hw_event.raw_type to 1.
160  * Bits that can be set in hw_event.read_format to request that
170 particular counter allowing one to take the round-robin scheduling effect
174 A "sampling" counter is one that is set up to generate an interrupt
180  * Bits that can be set in hw_event.record_type to request information
193 available to user-space using mmap() (see below).
201 applies to new descendents, not to any existing descendents at the
202 time the counter is created (nor to any new descendents of existing
206 on the CPU if at all possible.  It only applies to hardware counters
207 and only to group leaders.  If a pinned counter cannot be put onto the
215 In future, this will allow sophisticated monitoring programs to supply
216 extra configuration information via 'extra_config_len' to exploit
222 way to request that counting of events be restricted to times when the
226 operations, these can be used to relate userspace IP addresses to actual
233 The 'pid' parameter to the perf_event_open() system call allows the
234 counter to be specific to a task:
236  pid == 0: if the pid parameter is zero, the counter is attached to the
239  pid > 0: the counter is attached to a specific task (if the current task
240  has sufficient privilege to do so)
244 The 'cpu' parameter allows a counter to be made specific to a CPU:
246  cpu >= 0: the counter is restricted to a specific CPU
252 events of that task and 'follows' that task to whatever CPU the task
253 gets schedule to. Per task counters can be created by any user, for
261 The 'group_fd' parameter allows counter "groups" to be set up.  A
267 considered to be a group with only 1 member.)
272 can be meaningfully compared, added, divided (to get ratios), etc.,
293          * Bits needed to read the hw counters in user-space.
316         __s64   offset;                 /* add to hardware counter value */
346          * correlate userspace IPs to code. They have the following structure:
402 additionally set perf_event_attr.wakeup_events to generate one every
405 Future work will include a splice() interface to the ring-buffer.
410 events but does continue to exist and maintain its count value.
432 to enable a counter for 'nr' events, after which it gets disabled again.
435 attached to it, using prctl:
441 This applies to all counters on the current process, whether created
453 So to start with, in order to add HAVE_PERF_EVENTS to your Kconfig, you
460 weak stub hw_perf_event_init() to register hardware counters.
463 should select PERF_USE_VMALLOC in order to avoid these for perf mmap().