Lines Matching refs:be

11 One type of event for which EBBs can be configured is PMU exceptions. This
21 attr.config. All events which can be configured on the hardware PMU are
29 EBBs can only sensibly be used by programs for self-monitoring.
31 It is a feature of the perf_events API that events can be created on other
34 EBBs will ever be delivered.
38 and attach an EBB event to the process, which will then cause EBBs to be
44 events can be configured. This means that EBB events can not be run
48 kernel will in general schedule the EBB event, and perf will be notified that
53 events will be given priority over other events, unless they are also pinned.
55 first will be scheduled and the other will be put in error state. See the
65 EBB events must be created with a particular, and restrictive, set of
69 An EBB event must be created with the "pinned" and "exclusive" attributes set.
76 An EBB event must be attached to a task. This is specified to perf_event_open()
82 EBB events must specify the PMC they are to be counted on. This ensures
89 Once an EBB event has been successfully opened, it must be enabled with the
90 perf_events API. This can be achieved either via the ioctl() interface, or the
101 this case the enable will be successful. However if there is already an event
102 pinned on the PMU then the enable will not be successful.
117 regular event. If this is the last EBB event the PMU will be deconfigured and
118 no further PMU EBBs will be delivered.
124 The EBB handler is just regular userspace code, however it must be written in
126 are live (possibly) and so must be saved somehow before the handler can invoke