Home
last modified time | relevance | path

Searched refs:task (Results 1 – 25 of 27) sorted by relevance

12

/tools/testing/fault-injection/
Dfailcmd.sh33 --oom-kill-allocating-task=value
41 --interval=value, --space=value, --verbose=value, --task-filter=value,
86 LONGOPTS=probability:,interval:,times:,space:,verbose:,task-filter:
88 LONGOPTS=$LONGOPTS,reject-start:,reject-end:,oom-kill-allocating-task:,help
107 echo N > $FAULTATTR/task-filter
153 --task-filter)
177 --oom-kill-allocating-task)
212 echo $task_filter > $FAULTATTR/task-filter
/tools/perf/
Dbuiltin-sched.c242 get_new_event(struct task_desc *task, u64 timestamp) in get_new_event() argument
245 unsigned long idx = task->nr_events; in get_new_event()
251 task->nr_events++; in get_new_event()
252 size = sizeof(struct sched_atom *) * task->nr_events; in get_new_event()
253 task->atoms = realloc(task->atoms, size); in get_new_event()
254 BUG_ON(!task->atoms); in get_new_event()
256 task->atoms[idx] = event; in get_new_event()
261 static struct sched_atom *last_event(struct task_desc *task) in last_event() argument
263 if (!task->nr_events) in last_event()
266 return task->atoms[task->nr_events - 1]; in last_event()
[all …]
Ddesign.txt13 hardware capabilities. It provides per task and per CPU counters, counter
200 events on descendant tasks as well as the task specified. This only
234 counter to be specific to a task:
237 current task.
239 pid > 0: the counter is attached to a specific task (if the current task
251 A 'pid > 0' and 'cpu == -1' counter is a per task counter that counts
252 events of that task and 'follows' that task to whatever CPU the task
253 gets schedule to. Per task counters can be created by any user, for
Dbuiltin-inject.c515 evsel->attr.task; in has_tracking()
/tools/perf/tests/attr/
Dbase-record26 task=0
Dbase-stat26 task=0
/tools/perf/Documentation/
Dperf-inject.txt41 tasks slept. sched_switch contains a callchain where a task slept and
42 sched_stat contains a timeslice how long a task slept.
Dperf-timechart.txt19 and CPU events (task switches, running times, CPU power states, etc),
58 Print task info for at least given number of tasks.
66 interpreted as task name.
Dperf-sched.txt20 'perf sched latency' to report the per task scheduling latencies
Dperf-report.txt75 - comm: command (name) of the task which can be read via /proc/<pid>/comm
76 - pid: command and tid of the task
81 - cpu: cpu number the task ran at the time of sample
82 - socket: processor socket number the task ran at the time of sample
Dperf-script.txt229 --show-task-events
230 Display task related events (e.g. FORK, COMM, EXIT).
Dperf-trace.txt17 syscalls, but other system events like pagefaults, task lifetime events,
Dperf-stat.txt181 8117.370256 task clock ticks # 11.281 CPU utilization factor
Dperf-script-perl.txt100 $common_pid the pid of the current task
Dperf-script-python.txt73 Basically our task is to keep a per-syscall tally that gets updated
496 common_pid the pid of the current task
/tools/perf/python/
Dtwatch.py23 task = 1, comm = 1, mmap = 0, freq = 0,
/tools/perf/tests/
Dtask-exit.c84 evsel->attr.task = 1; in test__task_exit()
Dattr.c109 WRITE_ASS(task, "d"); in store_event()
DBuild23 perf-y += task-exit.o
/tools/testing/ktest/examples/
DREADME3 is broken up by task which makes it easier to understand how to set up
/tools/thermal/tmon/
DREADME17 matrix by hand is not a trivial task. Testing is also difficult in that
/tools/perf/scripts/python/
Dsched-migration.py127 next_tasks = [task for task in self.tasks if task != old]
/tools/perf/util/
Dpython.c608 task = 0, in pyrf_evsel__init() local
623 &enable_on_exec, &task, &watermark, in pyrf_evsel__init()
651 attr.task = task; in pyrf_evsel__init()
Dparse-events.l232 task-clock { return sym(yyscanner, PERF_TYPE_SOFTWARE, PERF_COUNT_SW_TASK_CLOCK); }
Devsel.c856 attr->task = track; in perf_evsel__config()
1264 PRINT_ATTRf(task, p_unsigned); in perf_event_attr__fprintf()

12