Home
last modified time | relevance | path

Searched refs:sched_switch (Results 1 – 25 of 28) sorted by relevance

12

/Linux-v5.10/tools/testing/selftests/ftrace/test.d/event/
Devent-enable.tc21 count=`cat trace | grep sched_switch | wc -l`
28 echo 1 > events/sched/sched_switch/enable
32 count=`cat trace | grep sched_switch | wc -l`
39 echo 0 > events/sched/sched_switch/enable
43 count=`cat trace | grep sched_switch | wc -l`
Devent-pid.tc22 echo 1 > events/sched/sched_switch/enable
26 count=`cat trace | grep sched_switch | wc -l`
41 count=`cat trace | grep sched_switch | grep -v "pid=$mypid" | wc -l`
50 echo 1 > events/sched/sched_switch/enable
54 count=`cat trace | grep sched_switch | grep -v "pid=$mypid" | wc -l`
/Linux-v5.10/tools/testing/selftests/ftrace/test.d/trigger/
Dtrigger-eventonoff.tc19 echo 0 > events/sched/sched_switch/enable
22 if [ `cat events/sched/sched_switch/enable` != '1*' ]; then
29 echo 1 > events/sched/sched_switch/enable
32 if [ `cat events/sched/sched_switch/enable` != '0*' ]; then
/Linux-v5.10/tools/testing/selftests/ftrace/test.d/trigger/inter-event/
Dtrigger-onmax-action-hist.tc21 …(next_comm,prev_pid,prev_prio,prev_comm) if next_comm=="ping"' >> events/sched/sched_switch/trigger
24 if ! grep -q "max:" events/sched/sched_switch/hist; then
Dtrigger-onmatch-onmax-action-hist.tc22 …(next_comm,prev_pid,prev_prio,prev_comm) if next_comm=="ping"' >> events/sched/sched_switch/trigger
26 …ing" events/synthetic/wakeup_latency/hist -o ! grep -q "max:" events/sched/sched_switch/hist]; then
Dtrigger-field-variable-support.tc15 …xt_pid,sched.sched_waking.prio,next_comm) if next_comm=="ping"' > events/sched/sched_switch/trigger
27 …t_pid,sched.sched_waking.prio,next_comm) if next_comm=="ping"' >> events/sched/sched_switch/trigger
Dtrigger-multi-actions-accept.tc14 TRIGGER2=events/sched/sched_switch/trigger
Dtrigger-onmatch-action-hist.tc22 …p_latency($wakeup_lat,next_pid,next_comm) if next_comm=="ping"' > events/sched/sched_switch/trigger
Dtrigger-trace-action-hist.tc22 …p_latency,$wakeup_lat,next_pid,next_comm) if next_comm=="ping"' > events/sched/sched_switch/trigger
Dtrigger-inter-event-combined-hist.tc26 …eup).wakeup_latency($wakeup_lat,next_pid) if next_comm=="ping"' > events/sched/sched_switch/trigger
/Linux-v5.10/Documentation/trace/
Dhistogram-design.rst360 pid, and later a sched_switch event that switches to that pid event
368 events/sched/sched_switch/trigger
574 sched_switch histogram | |
577 The sched_switch histogram paired with the above sched_waking | |
579 sched_switch histogram is that it references a variable on the | |
597 The diagram below describes the situation for the sched_switch | |
601 events/sched/sched_switch/trigger | |
705 So, in order to handle an event for the sched_switch histogram,
710 sched_switch histogram. For each one of those, the referenced
723 uses it in the sched_switch trigger. The sched_switch trigger also
[all …]
Dhistogram.rst1990 CPU by a sched_switch event (saved_pid matches next_pid), calculate
1997 /sys/kernel/debug/tracing/events/sched/sched_switch/trigger
2025 sched_waking and another for sched_switch, keyed on pid. Whenever
2041 /sys/kernel/debug/tracing/events/sched/sched_switch/trigger
2047 # cat /sys/kernel/debug/tracing/events/sched/sched_switch/hist
2084 sched_waking and another for sched_switch, keyed on pid. Whenever
2103 /sys/kernel/debug/tracing/events/sched/sched_switch/trigger
2112 # cat /sys/kernel/debug/tracing/events/sched/sched_switch/hist
2144 sched_switch events, which should match the time displayed in the
2149 …<...>-2103 [005] d..3 309.873125: sched_switch: prev_comm=cyclictest prev_pid=2103 prev_prio=19…
[all …]
Dftrace.rst283 Note, sched_switch and sched_wake_up will also trace events
294 Note, sched_switch and sched_wakeup will trace threads not listed
296 sched_switch or sched_wakeup events also trace a thread that should
1164 in the sched_switch trace point to fill comm cache
1172 in the sched_switch trace point to fill the cache of
3143 echo 'try_to_wake_up:enable_event:sched:sched_switch:2' > \
3153 echo '!try_to_wake_up:enable_event:sched:sched_switch:0' > \
3155 echo '!schedule:disable_event:sched:sched_switch' > \
3333 …<idle>-0 [005] d... 2440.603828: sched_switch: prev_comm=swapper/5 prev_pid=0 prev_prio=120 …
3334 …sleep-2242 [005] d... 2440.603846: sched_switch: prev_comm=snapshot-test-2 prev_pid=2242 prev_pr…
[all …]
Devents.rst263 # cat sched_switch/filter
273 # cat sched_switch/filter
284 # cat sched_switch/filter
418 kmem:kmalloc and sched:sched_switch, but can't have two kmem:kmalloc
/Linux-v5.10/tools/perf/scripts/python/
Dsched-migration.py104 def sched_switch(self, prev, prev_state, next): member in RunqueueSnapshot
179 def sched_switch(self, ts_list, prev, prev_state, next, cpu): member in TimeSlice
181 new_rq = old_rq.sched_switch(prev, prev_state, next)
333 def sched_switch(self, headers, prev_comm, prev_pid, prev_prio, prev_state, member in SchedEventProxy
349 ts.sched_switch(self.timeslices, prev_pid, prev_state, next_pid, headers.cpu)
427 parser.sched_switch(headers, prev_comm, prev_pid, prev_prio, prev_state,
/Linux-v5.10/tools/perf/scripts/perl/bin/
Dwakeup-latency-record2 perf record -e sched:sched_switch -e sched:sched_wakeup $@
/Linux-v5.10/tools/perf/scripts/python/bin/
Dsched-migration-record2 perf record -m 16384 -e sched:sched_wakeup -e sched:sched_wakeup_new -e sched:sched_switch -e sched…
/Linux-v5.10/tools/perf/tests/
Dswitch-tracking.c325 const char *sched_switch = "sched:sched_switch"; in test__switch_tracking() local
383 if (!perf_evlist__can_select_event(evlist, sched_switch)) { in test__switch_tracking()
389 err = parse_events(evlist, sched_switch, NULL); in test__switch_tracking()
391 pr_debug("Failed to parse event %s\n", sched_switch); in test__switch_tracking()
/Linux-v5.10/tools/perf/Documentation/
Dperf-inject.txt44 Merge sched_stat and sched_switch for getting events where and how long
45 tasks slept. sched_switch contains a callchain where a task slept and
Dperf-trace.txt81 _and_ sched:sched_switch to the 'A' cgroup, while:
85 will only set the sched:sched_switch event to the 'A' cgroup, all the
93 the syscall ones go to the 'A' cgroup, the sched:sched_switch goes
325 Trace the next two sched:sched_switch events, four block:*_plug events, the
330 0.000 :0/0 sched:sched_switch:swapper/2:0 [120] S ==> rcu_sched:10 [120]
331 0.015 rcu_sched/10 sched:sched_switch:rcu_sched:10 [120] R ==> swapper/2:0 [120]
Dperf-intel-pt.txt739 as the sched:sched_switch tracepoints will be used to receive such information:
751 sched_switch tracepoint
754 The sched_switch tracepoint is used to provide side-band data for Intel PT
758 The sched_switch events are automatically added. e.g. the second event shown
829 Note, the sched_switch event is only added if the user is permitted to use it
832 Note also, the sched_switch event is only added if TSC packets are requested.
833 That is because, in the absence of timing information, the sched_switch events
/Linux-v5.10/tools/perf/scripts/perl/
Dwakeup-latency.pl28 sub sched::sched_switch
/Linux-v5.10/tools/testing/selftests/ftrace/test.d/instances/
Dinstance-event.tc42 echo 1 > foo/events/sched/sched_switch
/Linux-v5.10/tools/perf/arch/x86/util/
Dintel-pt.c415 const char *sched_switch = "sched:sched_switch"; in intel_pt_track_switches() local
419 if (!perf_evlist__can_select_event(evlist, sched_switch)) in intel_pt_track_switches()
422 err = parse_events(evlist, sched_switch, NULL); in intel_pt_track_switches()
425 __func__, sched_switch, err); in intel_pt_track_switches()
/Linux-v5.10/include/trace/events/
Dsched.h138 TRACE_EVENT(sched_switch,

12