Lines Matching refs:events

6 CPUs. These registers count the number of certain types of hw events: such
9 trigger interrupts when a threshold number of events have passed - and can
65         __u32                   wakeup_events;  /* wakeup every n events */
100 	 * Common hardware events, generalized by the kernel:
111 These are standardized types of events that work relatively uniformly
119 and accessed as raw events.  For example, to count "External bus
120 cycles while bus lock signal asserted" events on Intel Core CPUs, pass
124 software events, selected by 'event_id':
129  * physical and sw events of the kernel (and allow the profiling of them as
146 /debug/tracing/events/*/*/id
151 number of events that occur, and is characterised by having
175 every N events, where N is given by 'irq_period'.  A sampling counter
192 Such (and other) events will be recorded in a ring-buffer, which is
200 events on descendant tasks as well as the task specified.  This only
222 way to request that counting of events be restricted to times when the
228 these events are recorded in the ring-buffer (see below).
252 events of that task and 'follows' that task to whatever CPU the task
257 all events on CPU-x. Per CPU counters need CAP_SYS_ADMIN privilege.
273 with each other, since they have counted events for the same set of
277 Like stated, asynchronous events, like counter overflow or PROT_EXEC mmap
330 The following 2^n pages are the ring-buffer which contains events of the form:
345          * The MMAP events record the PROT_EXEC mappings so that we can
398 Notification of new events is possible through poll()/select()/epoll() and
403 so many counter overflow events.
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.