Home
last modified time | relevance | path

Searched refs:workload (Results 1 – 17 of 17) sorted by relevance

/tools/perf/tests/
Dperf-record.c110 err = sched__get_first_possible_cpu(evlist->workload.pid, &cpu_mask); in test__PERF_RECORD()
122 if (sched_setaffinity(evlist->workload.pid, cpu_mask_size, &cpu_mask) < 0) { in test__PERF_RECORD()
203 if ((pid_t)sample.pid != evlist->workload.pid) { in test__PERF_RECORD()
205 name, evlist->workload.pid, sample.pid); in test__PERF_RECORD()
209 if ((pid_t)sample.tid != evlist->workload.pid) { in test__PERF_RECORD()
211 name, evlist->workload.pid, sample.tid); in test__PERF_RECORD()
220 (pid_t)event->comm.pid != evlist->workload.pid) { in test__PERF_RECORD()
Devent-times.c53 waitpid(evlist->workload.pid, NULL, 0); in detach__enable_on_exec()
/tools/perf/Documentation/
Dperf-sched.txt18 of an arbitrary workload.
21 and other scheduling properties of the workload.
23 'perf sched script' to see a detailed trace of the workload that
26 'perf sched replay' to simulate the workload that was recorded
28 that mimic the workload based on the events in the trace. These
30 of the workload as it occurred when it was recorded - and can repeat
34 workload captured via perf sched record. Columns stand for
Dperf-timechart.txt6 perf-timechart - Tool to visualize total system behavior during a workload
18 of an arbitrary workload. By default timechart records only scheduler
Dperf-kmem.txt18 of an arbitrary workload.
Dtips.txt7 Save output of perf stat using: perf stat record <target workload>
Dexamples.txt45 'repeat the workload N times' feature of perf stat:
65 Furthermore, these tracepoints can be used to sample the workload as
Dperf-kvm.txt24 of an arbitrary workload.
27 of an arbitrary workload and save it into a perf data file. We set the
Dperf-stat.txt217 if the workload is actually bound by the CPU and not by something else.
231 on workload with changing phases.
236 CPUs the workload runs on. If needed the CPUs can be forced using
Dintel-pt.txt565 workload only
568 workload).
570 "workload only" mode is selected by not using the other options but providing a
571 command to run (i.e. the workload).
580 In workload-only mode, the workload is traced but with per-cpu buffers.
581 Inheritance is allowed. Note that you can now trace a workload in per-thread
606 information to decode Intel PT in per-cpu mode, and potentially workload-only
607 mode too if the workload creates new processes.
Dperf-list.txt189 can cause measurement errors when the workload changes its execution
Dperf-script.txt23 'perf script' to see a detailed trace of the workload that was
Dperf-record.txt290 symbols if the workload binaries used when recording get locally rebuilt
/tools/perf/util/
Devlist.c52 evlist->workload.pid = -1; in perf_evlist__init()
1707 evlist->workload.pid = fork(); in perf_evlist__prepare_workload()
1708 if (evlist->workload.pid < 0) { in perf_evlist__prepare_workload()
1713 if (!evlist->workload.pid) { in perf_evlist__prepare_workload()
1777 thread_map__set_pid(evlist->threads, 0, evlist->workload.pid); in perf_evlist__prepare_workload()
1791 evlist->workload.cork_fd = go_pipe[1]; in perf_evlist__prepare_workload()
1806 if (evlist->workload.cork_fd > 0) { in perf_evlist__start_workload()
1812 ret = write(evlist->workload.cork_fd, &bf, 1); in perf_evlist__start_workload()
1816 close(evlist->workload.cork_fd); in perf_evlist__start_workload()
Devlist.h93 } workload; member
/tools/perf/
Dbuiltin-record.c672 thread_map = thread_map__new_by_tid(rec->evlist->workload.pid); in record__synthesize_workload()
1023 rec->evlist->workload.pid, in __cmd_record()
1043 rec->evlist->workload.pid, in __cmd_record()
1178 kill(rec->evlist->workload.pid, SIGTERM); in __cmd_record()
Dbuiltin-stat.c612 child_pid = evsel_list->workload.pid; in __run_perf_stat()