Home
last modified time | relevance | path

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

12

/linux/tools/testing/selftests/ftrace/test.d/event/
A 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`
A 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/tools/testing/selftests/ftrace/test.d/trigger/
A 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/Documentation/trace/
A Dhistogram-design.rst368 events/sched/sched_switch/trigger
710 sched_switch histogram. For each one of those, the referenced
723 uses it in the sched_switch trigger. The sched_switch trigger also
787 In this example, the sched_switch trigger has a reference to a
796 # cat events/sched/sched_switch/hist_debug
866 next_pid field on this sched_switch event, we retrieve the
1184 # cat events/sched/sched_switch/hist_debug
1458 # cat events/sched/sched_switch/hist_debug
1653 Here's the sched_switch trigger::
1756 # cat events/sched/sched_switch/hist_debug
[all …]
A Dhistogram.rst2085 CPU by a sched_switch event (saved_pid matches next_pid), calculate
2092 /sys/kernel/debug/tracing/events/sched/sched_switch/trigger
2120 sched_waking and another for sched_switch, keyed on pid. Whenever
2136 /sys/kernel/debug/tracing/events/sched/sched_switch/trigger
2142 # cat /sys/kernel/debug/tracing/events/sched/sched_switch/hist
2179 sched_waking and another for sched_switch, keyed on pid. Whenever
2198 /sys/kernel/debug/tracing/events/sched/sched_switch/trigger
2207 # cat /sys/kernel/debug/tracing/events/sched/sched_switch/hist
2239 sched_switch events, which should match the time displayed in the
2261 …<idle>-0 [007] d..3 309.874963: sched_switch: prev_comm=swapper/7 prev_pid=0 prev_prio=120 p…
[all …]
A 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
1170 in the sched_switch trace point to fill comm cache
1178 in the sched_switch trace point to fill the cache of
3148 echo 'try_to_wake_up:enable_event:sched:sched_switch:2' > \
3158 echo '!try_to_wake_up:enable_event:sched:sched_switch:0' > \
3160 echo '!schedule:disable_event:sched:sched_switch' > \
3413 # echo 1 > instances/foo/events/sched/sched_switch/enable
3435 …<idle>-0 [003] d..3 136.676909: sched_switch: prev_comm=swapper/3 prev_pid=0 prev_prio=120 p…
[all …]
A 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/tools/testing/selftests/ftrace/test.d/trigger/inter-event/
A 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
A 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
A 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
A Dtrigger-multi-actions-accept.tc14 TRIGGER2=events/sched/sched_switch/trigger
A Dtrigger-onmatch-action-hist.tc22 …p_latency($wakeup_lat,next_pid,next_comm) if next_comm=="ping"' > events/sched/sched_switch/trigger
A Dtrigger-trace-action-hist.tc22 …p_latency,$wakeup_lat,next_pid,next_comm) if next_comm=="ping"' > events/sched/sched_switch/trigger
A Dtrigger-inter-event-combined-hist.tc26 …eup).wakeup_latency($wakeup_lat,next_pid) if next_comm=="ping"' > events/sched/sched_switch/trigger
/linux/tools/perf/scripts/python/
A 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/tools/perf/tests/
A Dswitch-tracking.c326 const char *sched_switch = "sched:sched_switch"; in test__switch_tracking() local
387 if (!evlist__can_select_event(evlist, sched_switch)) { in test__switch_tracking()
393 err = parse_events(evlist, sched_switch, NULL); in test__switch_tracking()
395 pr_debug("Failed to parse event %s\n", sched_switch); in test__switch_tracking()
/linux/tools/perf/scripts/perl/bin/
A Dwakeup-latency-record2 perf record -e sched:sched_switch -e sched:sched_wakeup $@
/linux/tools/perf/scripts/python/bin/
A Dsched-migration-record2 perf record -m 16384 -e sched:sched_wakeup -e sched:sched_wakeup_new -e sched:sched_switch -e sched…
/linux/tools/perf/Documentation/
A 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
A 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]
A Dperf-intel-pt.txt754 as the sched:sched_switch tracepoints will be used to receive such information:
766 sched_switch tracepoint
769 The sched_switch tracepoint is used to provide side-band data for Intel PT
773 The sched_switch events are automatically added. e.g. the second event shown
844 Note, the sched_switch event is only added if the user is permitted to use it
847 Note also, the sched_switch event is only added if TSC packets are requested.
848 That is because, in the absence of timing information, the sched_switch events
/linux/tools/perf/scripts/perl/
A Dwakeup-latency.pl28 sub sched::sched_switch
/linux/tools/testing/selftests/ftrace/test.d/instances/
A Dinstance-event.tc42 echo 1 > foo/events/sched/sched_switch
/linux/tools/perf/arch/x86/util/
A Dintel-pt.c415 const char *sched_switch = "sched:sched_switch"; in intel_pt_track_switches() local
419 if (!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/include/trace/events/
A Dsched.h220 TRACE_EVENT(sched_switch,

Completed in 40 milliseconds

12