Lines Matching full:events

6 branch directly to a specified user space address when certain events occur.
20 Throughout this document we will refer to an "EBB event" or "EBB events". This
22 attr.config. All events which can be configured on the hardware PMU are
23 possible "EBB events".
32 It is a feature of the perf_events API that events can be created on other
34 events, however unless the target process enables EBBs (via mtspr(BESCR)) no
38 actually configure any events. At a later time another process can come along
45 events can be configured. This means that EBB events can not be run
46 concurrently with regular 'perf' commands, or any other perf events.
50 its events could not run.
52 The exclusion between EBB events and regular events is implemented using the
54 events will be given priority over other events, unless they are also pinned.
66 EBB events must be created with a particular, and restrictive, set of
71 Note that if you are creating a group of EBB events, only the leader can have
80 All events in a group must agree on whether they want EBB. That is all events
83 EBB events must specify the PMC they are to be counted on. This ensures
101 EBB event is enabled it will force all other non-pinned events off the PMU. In
136 EBB events are not inherited across fork. If the child process wishes to use