| /linux/tools/testing/selftests/thermal/intel/workload_hint/ |
| H A D | workload_hint_test.c | 39 perror("Unable to open workload type feature enable file"); in workload_hint_exit()
44 perror("Can't disable workload hints"); in workload_hint_exit()
48 printf("Disabled workload type prediction\n");
61 perror("Unable to open workload notification delay"); in main()
118 perror("Unable to open workload type feature enable file"); in main()
123 perror("Can't enable workload hints"); in main()
129 printf("Enabled workload type prediction\n"); in main()
134 perror("Unable to open workload type file"); in main()
173 printf("workload type slow:%s\n", "power");
175 printf("workload typ
[all...] |
| /linux/tools/perf/tests/shell/lib/ |
| H A D | perf_metric_validation.py | 22 \tis {1} in workload(s): {2} \n\
31 \tis {1} in workload(s): {2}\n\
39 workload='true', metrics='', cputype='cpu'): argument
49 self.workloads = [x for x in workload.split(",") if x]
51 self.allresults = dict() # metric results of all workload
55 self.results = dict() # metric results of current workload
188 # The first round collect_perf() run these metrics with simple workload
189 # "true". We give metrics a second chance with a longer workload if less
346 allres = [{"Workload": self.workloads[i], "Results": self.allresults[i]}
380 def _run_perf(self, metric, workload: str):
[all …]
|
| /linux/drivers/gpu/drm/i915/gvt/ |
| H A D | cmd_parser.c | 522 struct intel_vgpu_workload *workload; member
860 u32 base = s->workload->engine->mmio_base; in is_cmd_update_pdps()
868 struct intel_vgpu_mm *shadow_mm = s->workload->shadow_mm; in cmd_pdp_mmio_update_handler()
884 &s->workload->lri_shadow_mm); in cmd_pdp_mmio_update_handler()
1011 * In order to let workload with inhibit context to generate in cmd_reg_handler()
1013 * hw via LRIs in the workload with inhibit context. But as in cmd_reg_handler()
1014 * indirect context is loaded prior to LRIs in workload, we don't in cmd_reg_handler()
1017 * update reg values in it into vregs, so LRIs in workload with in cmd_reg_handler()
1024 s->workload->ring_context_gpa + 12, &ctx_sr_ctl, 4); in cmd_reg_handler()
1235 s->workload->pending_events); in cmd_handler_pipe_control()
[all …]
|
| H A D | scheduler.h | 89 /* if this workload has been dispatched to i915? */
91 bool shadow; /* if workload has done shadow of guest request */
137 void intel_vgpu_queue_workload(struct intel_vgpu_workload *workload);
164 void intel_vgpu_destroy_workload(struct intel_vgpu_workload *workload);
|
| H A D | sched_policy.c | 150 * after the flag is set, workload dispatch thread will in try_to_schedule_next_vgpu()
151 * stop dispatching workload for current vgpu in try_to_schedule_next_vgpu()
155 /* still have uncompleted workload? */ in try_to_schedule_next_vgpu()
172 /* wake up workload dispatch thread */ in try_to_schedule_next_vgpu()
184 /* search a vgpu with pending workload */ in find_busy_vgpu()
465 /* stop workload dispatching */ in intel_vgpu_stop_schedule()
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | idle_page_tracking.rst | 9 accessed by a workload and which are idle. This information can be useful for
10 estimating the workload's working set size, which, in turn, can be taken into
11 account when configuring the workload parameters, setting memory cgroup limits,
12 or deciding where to place the workload within a compute cluster.
51 workload one should:
53 1. Mark all the workload's pages as idle by setting corresponding bits in
55 ``/proc/pid/pagemap`` if the workload is represented by a process, or by
56 filtering out alien pages using ``/proc/kpagecgroup`` in case the workload
59 2. Wait until the workload accesses its working set.
|
| /linux/Documentation/filesystems/nfs/ |
| H A D | knfsd-stats.rst | 54 Depending on the NFS workload patterns and various network stack
58 However this is a more accurate and less workload-dependent measure
74 pool for the NFS workload (the workload is thread-limited), in which
76 performance of the NFS workload.
93 threads configured than can be used by the NFS workload. This is
99 slow; the idle timeout is 60 minutes. Unless the NFS workload
|
| /linux/tools/perf/tests/ |
| H A D | perf-record.c | 109 * Prepare the workload in argv[] to run, it'll fork it, and then wait in test__PERF_RECORD()
116 pr_debug("Couldn't run the workload!\n"); in test__PERF_RECORD()
129 err = sched__get_first_possible_cpu(evlist->workload.pid, cpu_mask); in test__PERF_RECORD()
142 if (sched_setaffinity(evlist->workload.pid, cpu_mask_size, cpu_mask) < 0) { in test__PERF_RECORD()
176 * count just on workload.pid, which will start... in test__PERF_RECORD()
231 if ((pid_t)sample.pid != evlist->workload.pid) { in test__PERF_RECORD()
233 name, evlist->workload.pid, sample.pid); in test__PERF_RECORD()
237 if ((pid_t)sample.tid != evlist->workload.pid) { in test__PERF_RECORD()
239 name, evlist->workload.pid, sample.tid); in test__PERF_RECORD()
248 (pid_t)event->comm.pid != evlist->workload.pid) { in test__PERF_RECORD()
|
| H A D | task-exit.c | 38 * This test will start a workload that does nothing then it checks
84 pr_debug("Couldn't run the workload!\n"); in test__task_exit()
155 TEST_CASE_EXCLUSIVE("Number of exit events of a simple workload", task_exit),
159 .desc = "Number of exit events of a simple workload",
|
| /linux/tools/perf/pmu-events/arch/x86/amdzen1/ |
| H A D | floating-point.json | 6 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
13 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
20 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
27 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
34 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
41 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
48 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
55 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
62 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
69 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
|
| /linux/drivers/platform/x86/amd/hfi/ |
| H A D | hfi.c | 94 * struct amd_hfi_cpuinfo - HFI workload class info per CPU
97 * @class_index: workload class ID index
98 * @nr_class: max number of workload class supported
100 * @amd_hfi_classes: current CPU workload class ranking data
271 * amd_hfi_online() - Enable workload classification on @cpu
272 * @cpu: CPU in which the workload classification will be enabled
303 * amd_hfi_offline() - Disable workload classification on @cpu
304 * @cpu: CPU in which the workload classification will be disabled
429 dev_err(dev, "failed to enable workload class config: %d\n", ret); in amd_hfi_pm_resume()
444 dev_err(dev, "failed to disable workload class config: %d\n", ret); in amd_hfi_pm_suspend()
|
| /linux/tools/perf/tests/shell/ |
| H A D | stat_bpf_counters.sh | 7 workload="perf test -w sqrtloop"
44 …base_instructions=$(perf stat --no-big-num -e instructions -- $workload 2>&1 | awk '/instructions/…
45 …bpf_instructions=$(perf stat --no-big-num --bpf-counters -e instructions -- $workload 2>&1 | awk …
54 …num -e instructions/name=base_instructions/,instructions/name=bpf_instructions/b -- $workload 2>&1)
|
| H A D | trace_summary.sh | 17 workload="true"
20 echo "testing: perf trace ${args} -- ${workload}"
21 perf trace ${args} -- ${workload} >${OUTPUT} 2>&1
|
| H A D | test_intel_pt.sh | 24 workload="${temp_dir}/workload"
64 cat << _end_of_file_ | /usr/bin/cc -o "${workload}" -xc - -pthread && have_workload=true
149 echo "No workload, so skipping"
255 $workload &
257 $workload &
259 echo "Workload PIDs are $w1 and $w2"
303 # Create a workload that uses self-modifying code and generates its own jitdump file
412 echo "SKIP: No jitdump workload"
|
| /linux/Documentation/admin-guide/ |
| H A D | workload-tracing.rst | 4 Discovering Linux kernel subsystems used by a workload
14 * Understanding system resources necessary to build and run a workload
17 in use by a workload. The completeness of the system usage information
18 depends on the completeness of coverage of a workload.
24 * Once we discover and understand the workload needs, we can focus on them
32 the system resources in use by a workload. Once we discover and understand
33 the workload needs, we can focus on them to avoid regressions and use it
37 the workload and doesn't include all the system calls that can be invoked
39 these system calls that are invoked. As an example, if a workload opens a
42 is a workload that provides full coverage of a workload then the method
[all …]
|
| /linux/Documentation/gpu/ |
| H A D | drm-compute.rst | 11 have their memory swapped out from them. Or they simply want their workload
19 waiting for the workload to complete. Effectively this terminates the workload
22 Since this is undesirable, there need to be mitigations to prevent a workload
|
| H A D | drm-vm-bind-async.rst | 43 * ``long-running workload``: A workload that may take more than the
106 fences gated by a long-running workload and used as in-syncobjs for the
116 workload itself, which is allowed by dma-fence rules, but rather for
140 buffers. The workload execution can then easily be pipelined behind
142 for a GPU semaphore embedded by UMD in the workload.
|
| /linux/tools/testing/selftests/sched_ext/ |
| H A D | peek_dsq.c | 24 * Background workload thread that sleeps and wakes rapidly to exercise
95 printf("Starting %d background workload threads...\n", NUM_WORKERS); in run()
100 SCX_ERR("Failed to create workload thread %d: %s", i, strerror(err)); in run()
119 /* Stop workload threads and cleanup */ in run()
132 SCX_ERR("Failed to join workload thread %d: %s", i, strerror(err)); in run()
137 printf("Background workload threads stopped.\n"); in run()
|
| /linux/Documentation/scheduler/ |
| H A D | sched-capacity.rst | 73 With a workload that periodically does a fixed amount of work, you will get an
104 Executing the same workload as described in 1.3.1, which each CPU running at its
112 workload on CPU1
152 One issue that needs to be taken into account is that a workload's duty cycle is
154 periodic workload at a given frequency F::
163 Now, consider running the *same* workload at frequency F/2::
185 identical workload on CPUs of different capacity values will yield different
193 Executing a given periodic workload on each CPU at their maximum frequency would
384 workload on CPU0
391 workload on CPU1
[all …]
|
| /linux/Documentation/timers/ |
| H A D | no_hz.rst | 52 However, if you are instead running a light workload with long idle
59 In addition, if you are running either a real-time workload or an HPC
60 workload with short iterations, the scheduling-clock interrupts can
61 degrade your applications performance. If this describes your workload,
203 but do not see any change in your workload's behavior. Is this because
204 your workload isn't affected that much by OS jitter, or is it because
215 possible, then you can conclude that your workload is not all that
291 constraining the workload. For example, the only way to eliminate
|
| /linux/tools/perf/pmu-events/arch/x86/amdzen2/ |
| H A D | floating-point.json | 6 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
13 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
20 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
27 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
34 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
|
| /linux/Documentation/admin-guide/pm/ |
| H A D | intel-speed-select.rst | 10 variety of diverse workload requirements.
82 This feature allows configuration of a server dynamically based on workload
216 workload, disable turbo::
220 Then runs a busy workload on all CPUs, for example::
262 level 0 to 2800 MHz at performance level 4. As a result, any workload, which can
540 the user control base frequency. If some critical workload threads demand
568 Before enabling Intel(R) SST-BF and measuring its impact on a workload
569 performance, execute some workload and measure performance and get a baseline
584 To compare, pick a multi-threaded workload where each thread can be scheduled on
588 Below, the workload is measuring average scheduler wakeup latency, so a lower
[all …]
|
| /linux/rust/pin-init/examples/ |
| H A D | static_init.rs | 93 let workload = 1_000; in main() localVariable
100 for _ in 0..workload { in main()
109 for _ in 0..workload { in main()
122 assert_eq!(*mtx.lock(), workload * thread_count * 2); in main()
|
| H A D | pthread_mutex.rs | 158 let workload = 1_000_000; in main() localVariable
165 for _ in 0..workload { in main()
170 for _ in 0..workload { in main()
182 assert_eq!(*mtx.lock(), workload * thread_count * 2); in main()
|
| /linux/tools/perf/pmu-events/arch/x86/amdzen3/ |
| H A D | floating-point.json | 6 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
13 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
20 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
27 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
34 … This event reflects how busy the FPU pipelines are and may be used for workload characterization.…
|