| /linux/drivers/gpu/drm/i915/gvt/ |
| H A D | execlist.c | 370 static int prepare_execlist_workload(struct intel_vgpu_workload *workload) in prepare_execlist_workload() argument
372 struct intel_vgpu *vgpu = workload->vgpu; in prepare_execlist_workload()
377 if (!workload->emulate_schedule_in) in prepare_execlist_workload()
380 ctx[0] = *get_desc_from_elsp_dwords(&workload->elsp_dwords, 0); in prepare_execlist_workload()
381 ctx[1] = *get_desc_from_elsp_dwords(&workload->elsp_dwords, 1); in prepare_execlist_workload()
383 ret = emulate_execlist_schedule_in(&s->execlist[workload->engine->id], in prepare_execlist_workload()
392 static int complete_execlist_workload(struct intel_vgpu_workload *workload) in complete_execlist_workload() argument
394 struct intel_vgpu *vgpu = workload->vgpu; in complete_execlist_workload()
397 &s->execlist[workload->engine->id]; in complete_execlist_workload()
399 struct list_head *next = workload_q_head(vgpu, workload->engine)->next; in complete_execlist_workload()
[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 | trace.h | 231 void *workload, const char *cmd_name),
234 buf_addr_type, workload, cmd_name),
243 __field(void*, workload)
255 __entry->workload = workload;
261 …ring %d: address_type %u, buf_type %u, ip_gma %08x,cmd (name=%s,len=%u,raw cmd=%s), workload=%p\n",
271 __entry->workload)
|
| /linux/tools/testing/selftests/thermal/intel/workload_hint/ |
| H A D | workload_hint_test.c | 35 perror("Unable to open workload type feature enable file"); in workload_hint_exit()
40 perror("Can't disable workload hints"); in workload_hint_exit()
44 printf("Disabled workload type prediction\n"); in workload_hint_exit()
73 perror("Unable to open workload notification delay"); in main()
95 perror("Unable to open workload type feature enable file"); in main()
100 perror("Can't enable workload hints"); in main()
106 printf("Enabled workload type prediction\n"); in main()
111 perror("Unable to open workload type file"); in main()
150 printf("Invalid workload type index\n"); in main()
152 printf("workload typ in main()
[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/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/drivers/thermal/intel/int340x_thermal/ |
| H A D | processor_thermal_wt_hint.c | 3 * processor thermal device interface for reading workload type hints
7 * When user space enables workload type prediction:
12 * - The predicted workload type can be read from MMIO:
14 * active for change in workload type and also
15 * predicted workload type.
20 * Check if the interrupt is for change in workload type. Called from
26 * workload type.
51 /* Show current predicted workload type index */
162 /* If the workload hint was already enabled, then update with the new delay */ in notification_delay_ms_store()
|
| /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/Documentation/accel/qaic/ |
| H A D | qaic.rst | 18 if the workload is particularly quick, and the host is responsive. If the host
22 workload's ability to process inputs. The lprnet (license plate reader network)
23 workload is known to trigger this condition, and can generate in excess of 100k
32 sleep for a time to see if the workload will generate more activity. The IRQ
39 workload throughput performance (within run to run noise variation).
112 or receive data from a workload. The call will return a GEM handle that
123 get sent where to a workload. This requires a set of DMA transfers for the
166 workload should be allowed to interface with the DBC.
|
| /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
|
| /linux/drivers/platform/x86/amd/hfi/ |
| H A D | hfi.c | 95 * struct amd_hfi_cpuinfo - HFI workload class info per CPU
99 * @class_index: workload class ID index
100 * @nr_class: max number of workload class supported
102 * @amd_hfi_classes: current CPU workload class ranking data
274 * amd_hfi_online() - Enable workload classification on @cpu
275 * @cpu: CPU in which the workload classification will be enabled
311 * amd_hfi_offline() - Disable workload classification on @cpu
312 * @cpu: CPU in which the workload classification will be disabled
439 dev_err(dev, "failed to enable workload class config: %d\n", ret); in amd_hfi_pm_resume()
454 dev_err(dev, "failed to disable workload class config: %d\n", ret); in amd_hfi_pm_suspend()
|
| /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/Documentation/driver-api/thermal/ |
| H A D | intel_dptf.rst | 186 Available workload types. User space can specify one of the workload type
191 User space can specify any one of the available workload type using
359 Workload Type Hints
363 workload type and passing hints regarding it to the OS. A special sysfs
364 interface is provided to allow user space to obtain workload type hints from
376 Enable firmware to send workload type hints to user space.
381 the workload type prediction in the firmware and notifying the OS about
388 Predicted workload type index. User space can get notification of
|
| /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/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()
|
| /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/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.…
|
| /linux/Documentation/tools/rtla/ |
| H A D | common_timerlat_options.rst | 58 Set timerlat to run without a workload, and then dispatches user-space workloads
59 to wait on the timerlat_fd. Once the workload is awakes, it goes to sleep again
65 Set timerlat to run without workload, waiting for the user to dispatch a per-cpu
|