| /Linux-v5.4/drivers/net/ethernet/mellanox/mlx5/core/ |
| D | events.c | 15 /* General events handlers for the low level mlx5_core driver
17 * Other Major feature specific events such as
26 /* handler which forwards the event to events->nh, driver notifiers */
30 /* Events to be proccessed by mlx5_core */
36 /* Events to be forwarded (as is) to mlx5 core interfaces (mlx5e/mlx5_ib) */
39 /* QP/WQ resource events to forward */
49 /* SRQ events */
60 /* port module events stats */
136 /* handles all FW events, type == eqe->type */
141 struct mlx5_events *events = event_nb->ctx; in any_notifier() local
[all …]
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-bus-iio | 15 based on hardware generated events (e.g. data ready) or
40 buffered samples and events for device X.
603 What: /sys/bus/iio/devices/iio:deviceX/events
607 Configuration of which hardware generated events are passed up
610 What: /sys/.../iio:deviceX/events/in_accel_x_thresh_rising_en
611 What: /sys/.../iio:deviceX/events/in_accel_x_thresh_falling_en
612 What: /sys/.../iio:deviceX/events/in_accel_y_thresh_rising_en
613 What: /sys/.../iio:deviceX/events/in_accel_y_thresh_falling_en
614 What: /sys/.../iio:deviceX/events/in_accel_z_thresh_rising_en
615 What: /sys/.../iio:deviceX/events/in_accel_z_thresh_falling_en
[all …]
|
| D | sysfs-bus-event_source-devices-events | 1 What: /sys/devices/cpu/events/
2 /sys/devices/cpu/events/branch-misses
3 /sys/devices/cpu/events/cache-references
4 /sys/devices/cpu/events/cache-misses
5 /sys/devices/cpu/events/stalled-cycles-frontend
6 /sys/devices/cpu/events/branch-instructions
7 /sys/devices/cpu/events/stalled-cycles-backend
8 /sys/devices/cpu/events/instructions
9 /sys/devices/cpu/events/cpu-cycles
15 Description: Generic performance monitoring events
[all …]
|
| /Linux-v5.4/tools/testing/selftests/powerpc/pmu/ |
| D | count_instructions.c | 29 static int do_count_loop(struct event *events, u64 instructions, in do_count_loop() argument
42 event_read(&events[0]); in do_count_loop()
43 event_read(&events[1]); in do_count_loop()
46 difference = events[0].result.value - expected; in do_count_loop()
47 percentage = (double)difference / events[0].result.value * 100; in do_count_loop()
50 event_report(&events[0]); in do_count_loop()
51 event_report(&events[1]); in do_count_loop()
55 printf("Actual %llu\n", events[0].result.value); in do_count_loop()
59 event_reset(&events[0]); in do_count_loop()
60 event_reset(&events[1]); in do_count_loop()
[all …]
|
| D | per_event_excludes.c | 25 struct event *e, events[4]; in per_event_excludes() local
34 * We need to create the events disabled, otherwise the running/enabled in per_event_excludes()
37 e = &events[0]; in per_event_excludes()
42 e = &events[1]; in per_event_excludes()
49 e = &events[2]; in per_event_excludes()
56 e = &events[3]; in per_event_excludes()
63 FAIL_IF(event_open(&events[0])); in per_event_excludes()
68 * and we're asking for the events to be in a group. in per_event_excludes()
71 FAIL_IF(event_open_with_group(&events[i], events[0].fd)); in per_event_excludes()
86 FAIL_IF(event_read(&events[i])); in per_event_excludes()
[all …]
|
| /Linux-v5.4/tools/perf/pmu-events/ |
| D | README | 2 The contents of this directory allow users to specify PMU events in their
9 tree tools/perf/pmu-events/arch/foo.
12 JSON files, each of which describes a set of PMU events.
14 - The CSV file that maps a specific CPU to its set of PMU events is to
21 events", defined in architecture standard JSONs.
25 The PMU events supported by a CPU model are expected to grouped into topics
26 such as Pipelining, Cache, Memory, Floating-point etc. All events for a topic
33 $ ls tools/perf/pmu-events/arch/x86/silvermont
42 'pmu-events.c', which encodes the two sets of tables:
44 - Set of 'PMU events tables' for all known CPUs in the architecture,
[all …]
|
| D | Build | 5 pmu-events-y += pmu-events.o
6 JDIR = pmu-events/arch/$(SRCARCH)
11 # Locate/process JSON files in pmu-events/arch/
12 # directory and create tables in pmu-events.c.
14 $(OUTPUT)pmu-events/pmu-events.c: $(JSON) $(JEVENTS)
15 $(Q)$(call echo-cmd,gen)$(JEVENTS) $(SRCARCH) pmu-events/arch $(OUTPUT)pmu-events/pmu-events.c $(V)
|
| /Linux-v5.4/lib/ |
| D | flex_proportions.c | 14 * Where x_{i,j} is j's number of events in i-th last time period and x_i is
15 * total number of events in i-th last time period.
43 /* Use 1 to avoid dealing with periods with 0 events... */ in fprop_global_init()
44 err = percpu_counter_init(&p->events, 1, gfp); in fprop_global_init()
53 percpu_counter_destroy(&p->events); in fprop_global_destroy()
61 * if aging zeroed out all events. This can be used to detect whether declaring
66 s64 events; in fprop_new_period() local
70 events = percpu_counter_sum(&p->events); in fprop_new_period()
72 * Don't do anything if there are no events. in fprop_new_period()
74 if (events <= 1) { in fprop_new_period()
[all …]
|
| /Linux-v5.4/tools/testing/selftests/ftrace/test.d/trigger/ |
| D | trigger-filter.tc | 11 if [ ! -f set_event -o ! -d events/sched ]; then
16 if [ ! -f events/sched/sched_process_fork/trigger ]; then
23 echo 'traceoff if child_pid == 0' > events/sched/sched_process_fork/trigger
32 ! echo 'traceoff if a' > events/sched/sched_process_fork/trigger
33 ! echo 'traceoff if common_pid=0' > events/sched/sched_process_fork/trigger
34 ! echo 'traceoff if common_pid==b' > events/sched/sched_process_fork/trigger
35 echo 'traceoff if common_pid == 0' > events/sched/sched_process_fork/trigger
36 echo '!traceoff' > events/sched/sched_process_fork/trigger
37 ! echo 'traceoff if common_pid == child_pid' > events/sched/sched_process_fork/trigger
38 echo 'traceoff if common_pid <= 0' > events/sched/sched_process_fork/trigger
[all …]
|
| D | trigger-eventonoff.tc | 11 if [ ! -f set_event -o ! -d events/sched ]; then
16 if [ ! -f events/sched/sched_process_fork/trigger ]; then
21 FEATURE=`grep enable_event events/sched/sched_process_fork/trigger`
28 echo 0 > events/sched/sched_switch/enable
29 echo 'enable_event:sched:sched_switch' > events/sched/sched_process_fork/trigger
31 if [ `cat events/sched/sched_switch/enable` != '1*' ]; then
38 echo 1 > events/sched/sched_switch/enable
39 echo 'disable_event:sched:sched_switch' > events/sched/sched_process_fork/trigger
41 if [ `cat events/sched/sched_switch/enable` != '0*' ]; then
48 ! echo 'enable_event:nogroup:noevent' > events/sched/sched_process_fork/trigger
[all …]
|
| D | trigger-multihist.tc | 11 if [ ! -f set_event -o ! -d events/sched ]; then
16 if [ ! -f events/sched/sched_process_fork/trigger ]; then
21 if [ ! -f events/sched/sched_process_fork/hist ]; then
28 echo 'hist:keys=parent_pid:vals=child_pid' > events/sched/sched_process_fork/trigger
29 echo 'hist:keys=parent_comm:vals=child_pid' >> events/sched/sched_process_fork/trigger
31 grep parent_pid events/sched/sched_process_fork/hist > /dev/null || \
33 grep child events/sched/sched_process_fork/hist > /dev/null || \
36 grep "parent_comm: $COMM" events/sched/sched_process_fork/hist > /dev/null || \
43 echo 'hist:name=test_hist:keys=common_pid' > events/sched/sched_process_fork/trigger
45 grep test_hist events/sched/sched_process_fork/hist > /dev/null || \
[all …]
|
| D | trigger-hist.tc | 11 if [ ! -f set_event -o ! -d events/sched ]; then
16 if [ ! -f events/sched/sched_process_fork/trigger ]; then
21 if [ ! -f events/sched/sched_process_fork/hist ]; then
28 echo 'hist:keys=parent_pid:vals=child_pid' > events/sched/sched_process_fork/trigger
30 grep parent_pid events/sched/sched_process_fork/hist > /dev/null || \
32 grep child events/sched/sched_process_fork/hist > /dev/null || \
39 echo 'hist:keys=parent_pid,child_pid' > events/sched/sched_process_fork/trigger
41 grep '^{ parent_pid:.*, child_pid:.*}' events/sched/sched_process_fork/hist > /dev/null || \
48 echo 'hist:keys=parent_comm' > events/sched/sched_process_fork/trigger
51 grep "parent_comm: $COMM" events/sched/sched_process_fork/hist > /dev/null || \
[all …]
|
| /Linux-v5.4/Documentation/trace/ |
| D | events.rst | 26 The events which are available for tracing can be found in the file
34 .. Note:: '>>' is necessary, otherwise it will firstly disable all the events.
41 To disable all events, echo an empty line to the set_event file::
45 To enable all events, echo ``*:*`` or ``*:`` to the set_event file::
49 The events are organized into subsystems, such as ext4, irq, sched,
52 file. All of the events in a subsystem can be specified via the syntax
53 ``<subsystem>:*``; for example, to enable all irq events, you can use the
61 The events available are also listed in /sys/kernel/debug/tracing/events/ hierarchy
66 # echo 1 > /sys/kernel/debug/tracing/events/sched/sched_wakeup/enable
70 # echo 0 > /sys/kernel/debug/tracing/events/sched/sched_wakeup/enable
[all …]
|
| D | tracepoint-analysis.rst | 2 Notes on Analysing Behaviour Using Events and Tracepoints
13 Simplistically, tracepoints represent important events that can be
16 gathering and interpreting these events. Lacking any current Best Practises,
23 2. Listing Available Events
29 All possible events are visible from /sys/kernel/debug/tracing/events. Simply
32 $ find /sys/kernel/debug/tracing/events -type d
34 will give a fair indication of the number of events available.
39 Discovery and enumeration of all counters and events, including tracepoints,
40 are available with the perf tool. Getting a list of available events is a
52 3. Enabling Events
[all …]
|
| /Linux-v5.4/tools/perf/Documentation/ |
| D | itrace.txt | 1 i synthesize instructions events
2 b synthesize branches events
3 c synthesize branches events (calls only)
4 r synthesize branches events (returns only)
5 x synthesize transactions events
6 w synthesize ptwrite events
7 p synthesize power events
8 o synthesize other events recorded due to the use
10 e synthesize error events
14 s skip initial number of events
[all …]
|
| D | perf-list.txt | 36 Print how named events are resolved internally into perf events, and also
43 Events can optionally have a modifier by appending a colon and one or
44 more modifiers. Modifiers allow the user to restrict the events to be
74 clocks not halted) and 0xC1 (micro-ops retired). Both events map to
142 Events on these PMUs generally cannot be sampled, but only counted globally
153 and adding the values together. To simplify creation of multiple events,
168 For non root users generally only context switched PMU events are available.
169 This is normally only the events in the cpu PMU, the predefined events
170 like cycles and instructions and some software events.
176 sysctl to -1, which allows non root to use these events.
[all …]
|
| D | perf-script.txt | 31 'perf script record <script> <command>' to record the events required
34 language extension. If <command> is not specified, the events are
46 record the events required for <script> and to run the <script>
50 not specified, the events are recorded using the -a (system-wide)
59 'perf script <top-script>' to both record the events required for
113 Do various checks like samples ordering and lost events.
147 The first -F suppresses trace events (field list is ""), but then the
151 "Overriding previous field request for all events."
157 The first -F sets the fields for all events and the second -F
158 suppresses trace events. The user is given a warning message about
[all …]
|
| D | perf-trace.txt | 16 This command will show the events associated with the target, initially
17 syscalls, but other system events like pagefaults, task lifetime events,
18 scheduling events, etc.
22 but the session needs to include the raw_syscalls events (-e 'raw_syscalls:*').
24 automatically include the raw_syscalls events when writing events to a file.
39 List of syscalls and other perf events (tracepoints, HW cache events,
41 See 'perf list' for a complete list of events.
56 Record events on existing process ID (comma separated list).
60 Record events on existing thread ID (comma separated list).
64 Record events in threads owned by uid. Name or number.
[all …]
|
| /Linux-v5.4/tools/testing/selftests/powerpc/pmu/ebb/ |
| D | multi_counter_test.c | 14 * Test counting multiple events using EBBs.
18 struct event events[6]; in multi_counter() local
23 event_init_named(&events[0], 0x1001C, "PM_CMPLU_STALL_THRD"); in multi_counter()
24 event_init_named(&events[1], 0x2D016, "PM_CMPLU_STALL_FXU"); in multi_counter()
25 event_init_named(&events[2], 0x30006, "PM_CMPLU_STALL_OTHER_CMPL"); in multi_counter()
26 event_init_named(&events[3], 0x4000A, "PM_CMPLU_STALL"); in multi_counter()
27 event_init_named(&events[4], 0x600f4, "PM_RUN_CYC"); in multi_counter()
28 event_init_named(&events[5], 0x500fa, "PM_RUN_INST_CMPL"); in multi_counter()
30 event_leader_ebb_init(&events[0]); in multi_counter()
32 event_ebb_init(&events[i]); in multi_counter()
[all …]
|
| /Linux-v5.4/drivers/media/pci/cx23885/ |
| D | cx23885-ir.c | 28 u32 events = 0; in cx23885_ir_rx_work_handler() local
32 events |= V4L2_SUBDEV_IR_RX_SW_FIFO_OVERRUN; in cx23885_ir_rx_work_handler()
34 events |= V4L2_SUBDEV_IR_RX_HW_FIFO_OVERRUN; in cx23885_ir_rx_work_handler()
36 events |= V4L2_SUBDEV_IR_RX_END_OF_RX_DETECTED; in cx23885_ir_rx_work_handler()
38 events |= V4L2_SUBDEV_IR_RX_FIFO_SERVICE_REQ; in cx23885_ir_rx_work_handler()
40 if (events == 0) in cx23885_ir_rx_work_handler()
44 cx23885_input_rx_work_handler(dev, events); in cx23885_ir_rx_work_handler()
51 u32 events = 0; in cx23885_ir_tx_work_handler() local
55 events |= V4L2_SUBDEV_IR_TX_FIFO_SERVICE_REQ; in cx23885_ir_tx_work_handler()
57 if (events == 0) in cx23885_ir_tx_work_handler()
[all …]
|
| /Linux-v5.4/Documentation/powerpc/ |
| D | pmu-ebb.rst | 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.
[all …]
|
| /Linux-v5.4/drivers/scsi/lpfc/ |
| D | lpfc_logmsg.h | 23 #define LOG_ELS 0x00000001 /* ELS events */
24 #define LOG_DISCOVERY 0x00000002 /* Link discovery events */
25 #define LOG_MBOX 0x00000004 /* Mailbox events */
26 #define LOG_INIT 0x00000008 /* Initialization events */
27 #define LOG_LINK_EVENT 0x00000010 /* Link events */
30 #define LOG_NODE 0x00000080 /* Node table events */
31 #define LOG_TEMP 0x00000100 /* Temperature sensor events */
32 #define LOG_BG 0x00000200 /* BlockGuard events */
33 #define LOG_MISC 0x00000400 /* Miscellaneous events */
34 #define LOG_SLI 0x00000800 /* SLI events */
[all …]
|
| /Linux-v5.4/tools/lib/traceevent/Documentation/ |
| D | libtraceevent-event_list.txt | 7 Get list of events, sorted by given criteria.
27 The _tep_list_events()_ function returns an array of pointers to the events,
46 The _tep_list_events()_ function returns an array of pointers to events.
50 The _tep_list_events_copy()_ function returns an array of pointers to events.
63 struct tep_event_format **events;
66 events = tep_list_events(tep, TEP_EVENT_SORT_ID);
67 if (events == NULL) {
68 /* Failed to get the events, sorted by ID */
70 while(events[i]) {
71 /* walk through the list of the events, sorted by ID */
[all …]
|
| /Linux-v5.4/Documentation/media/kapi/ |
| D | v4l2-event.rst | 3 V4L2 events
6 The V4L2 events provide a generic way to pass events to user space.
7 The driver must use :c:type:`v4l2_fh` to be able to support V4L2 events.
9 Events are subscribed per-filehandle. An event specification consists of a
14 The :c:type:`v4l2_fh` struct has a list of subscribed events on its
23 of :c:func:`v4l2_event_subscribe`. This ringbuffer is used to store any events
28 generating lots of events of one type in a short time, then that will
29 not overwrite events of another type.
31 But if you get more events of one type than the size of the
47 - struct :c:type:`v4l2_fh` has two lists: one of the ``subscribed`` events,
[all …]
|
| /Linux-v5.4/Documentation/input/ |
| D | event-codes.rst | 12 A single hardware event generates multiple input events. Each input event
14 used to separate input events into packets of input data changes occurring at
18 The input protocol is a stateful protocol. Events are emitted only when values
31 type has a set of applicable codes to be used in generating events. See the
36 - Used as markers to separate events. Events may be separated in time or in
99 - Used to synchronize and separate events into packets of input data changes
110 - Used to synchronize and separate touch events. See the
116 Client should ignore all events up to and including next SYN_REPORT
123 EV_KEY events take the form KEY_<name> or BTN_<name>. For example, KEY_A is used
126 emitted with value 0. Some hardware send events when a key is repeated. These
[all …]
|
