| /Linux-v5.4/drivers/gpu/drm/i915/gvt/ |
| D | scheduler.c | 58 static void update_shadow_pdps(struct intel_vgpu_workload *workload) in update_shadow_pdps() argument
61 workload->req->hw_context->state->obj; in update_shadow_pdps()
65 if (WARN_ON(!workload->shadow_mm)) in update_shadow_pdps()
68 if (WARN_ON(!atomic_read(&workload->shadow_mm->pincount))) in update_shadow_pdps()
74 (void *)workload->shadow_mm->ppgtt_mm.shadow_pdps); in update_shadow_pdps()
83 static void sr_oa_regs(struct intel_vgpu_workload *workload, in sr_oa_regs() argument
86 struct drm_i915_private *dev_priv = workload->vgpu->gvt->dev_priv; in sr_oa_regs()
100 if (workload->ring_id != RCS0) in sr_oa_regs()
104 workload->oactxctrl = reg_state[ctx_oactxctrl + 1]; in sr_oa_regs()
106 for (i = 0; i < ARRAY_SIZE(workload->flex_mmio); i++) { in sr_oa_regs()
[all …]
|
| D | execlist.c | 377 static int prepare_execlist_workload(struct intel_vgpu_workload *workload) in prepare_execlist_workload() argument
379 struct intel_vgpu *vgpu = workload->vgpu; in prepare_execlist_workload()
382 int ring_id = workload->ring_id; in prepare_execlist_workload()
385 if (!workload->emulate_schedule_in) in prepare_execlist_workload()
388 ctx[0] = *get_desc_from_elsp_dwords(&workload->elsp_dwords, 0); in prepare_execlist_workload()
389 ctx[1] = *get_desc_from_elsp_dwords(&workload->elsp_dwords, 1); in prepare_execlist_workload()
399 static int complete_execlist_workload(struct intel_vgpu_workload *workload) in complete_execlist_workload() argument
401 struct intel_vgpu *vgpu = workload->vgpu; in complete_execlist_workload()
402 int ring_id = workload->ring_id; in complete_execlist_workload()
410 gvt_dbg_el("complete workload %p status %d\n", workload, in complete_execlist_workload()
[all …]
|
| D | cmd_parser.c | 498 struct intel_vgpu_workload *workload; member
931 s->workload->ring_context_gpa + 12, &ctx_sr_ctl, 4); in cmd_reg_handler()
1157 s->workload->pending_events); in cmd_handler_pipe_control()
1164 s->workload->pending_events); in cmd_handler_mi_user_interrupt()
1678 s->workload->pending_events); in cmd_handler_mi_flush_dw()
1743 s->vgpu->gtt.ggtt_mm : s->workload->shadow_mm; in find_bb_size()
1759 "ppgtt" : "ggtt", s->ring_id, s->workload); in find_bb_size()
1771 "ppgtt" : "ggtt", s->ring_id, s->workload); in find_bb_size()
1805 "ppgtt" : "ggtt", s->ring_id, s->workload); in audit_bb_end()
1826 s->vgpu->gtt.ggtt_mm : s->workload->shadow_mm; in perform_bb_shadow()
[all …]
|
| 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;
271 __entry->workload)
|
| D | scheduler.h | 135 void intel_vgpu_queue_workload(struct intel_vgpu_workload *workload);
161 void intel_vgpu_destroy_workload(struct intel_vgpu_workload *workload);
|
| D | cmd_parser.h | 45 int intel_gvt_scan_and_shadow_ringbuffer(struct intel_vgpu_workload *workload);
|
| /Linux-v5.4/tools/perf/tests/ |
| D | perf-record.c | 113 err = sched__get_first_possible_cpu(evlist->workload.pid, &cpu_mask); in test__PERF_RECORD()
125 if (sched_setaffinity(evlist->workload.pid, cpu_mask_size, &cpu_mask) < 0) { in test__PERF_RECORD()
211 if ((pid_t)sample.pid != evlist->workload.pid) { in test__PERF_RECORD()
213 name, evlist->workload.pid, sample.pid); in test__PERF_RECORD()
217 if ((pid_t)sample.tid != evlist->workload.pid) { in test__PERF_RECORD()
219 name, evlist->workload.pid, sample.tid); in test__PERF_RECORD()
228 (pid_t)event->comm.pid != evlist->workload.pid) { in test__PERF_RECORD()
|
| D | event-times.c | 55 waitpid(evlist->workload.pid, NULL, 0); in detach__enable_on_exec()
|
| /Linux-v5.4/tools/perf/Documentation/ |
| D | perf-sched.txt | 18 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
|
| D | perf-timechart.txt | 6 perf-timechart - Tool to visualize total system behavior during a workload
18 of an arbitrary workload. By default timechart records only scheduler
|
| D | examples.txt | 45 'repeat the workload N times' feature of perf stat:
65 Furthermore, these tracepoints can be used to sample the workload as
|
| D | perf-kmem.txt | 18 of an arbitrary workload.
|
| D | perf-kvm.txt | 24 of an arbitrary workload.
27 of an arbitrary workload and save it into a perf data file. We set the
|
| /Linux-v5.4/Documentation/admin-guide/mm/ |
| D | idle_page_tracking.rst | 11 accessed by a workload and which are idle. This information can be useful for
12 estimating the workload's working set size, which, in turn, can be taken into
13 account when configuring the workload parameters, setting memory cgroup limits,
14 or deciding where to place the workload within a compute cluster.
53 workload one should:
55 1. Mark all the workload's pages as idle by setting corresponding bits in
57 ``/proc/pid/pagemap`` if the workload is represented by a process, or by
58 filtering out alien pages using ``/proc/kpagecgroup`` in case the workload
61 2. Wait until the workload accesses its working set.
|
| /Linux-v5.4/Documentation/filesystems/nfs/ |
| D | knfsd-stats.txt | 52 Depending on the NFS workload patterns and various network stack
56 However this is a more accurate and less workload-dependent measure
72 pool for the NFS workload (the workload is thread-limited), in which
74 performance of the NFS workload.
91 threads configured than can be used by the NFS workload. This is
97 slow; the idle timeout is 60 minutes. Unless the NFS workload
|
| /Linux-v5.4/drivers/gpu/drm/amd/powerplay/hwmgr/ |
| D | pp_psm.c | 263 long workload; in psm_adjust_power_state_dynamic() local
286 workload = hwmgr->workload_setting[index]; in psm_adjust_power_state_dynamic()
288 if (hwmgr->power_profile_mode != workload && hwmgr->hwmgr_func->set_power_profile_mode) in psm_adjust_power_state_dynamic()
289 hwmgr->hwmgr_func->set_power_profile_mode(hwmgr, &workload, 0); in psm_adjust_power_state_dynamic()
|
| /Linux-v5.4/drivers/gpu/drm/amd/powerplay/inc/ |
| D | smu_v11_0.h | 63 #define WORKLOAD_MAP(profile, workload) \ argument
64 [profile] = {1, (workload)}
|
| /Linux-v5.4/tools/perf/util/ |
| D | evlist.c | 61 evlist->workload.pid = -1; in evlist__init()
1287 evlist->workload.pid = fork(); in perf_evlist__prepare_workload()
1288 if (evlist->workload.pid < 0) { in perf_evlist__prepare_workload()
1293 if (!evlist->workload.pid) { in perf_evlist__prepare_workload()
1357 perf_thread_map__set_pid(evlist->core.threads, 0, evlist->workload.pid); in perf_evlist__prepare_workload()
1371 evlist->workload.cork_fd = go_pipe[1]; in perf_evlist__prepare_workload()
1386 if (evlist->workload.cork_fd > 0) { in perf_evlist__start_workload()
1392 ret = write(evlist->workload.cork_fd, &bf, 1); in perf_evlist__start_workload()
1396 close(evlist->workload.cork_fd); in perf_evlist__start_workload()
|
| /Linux-v5.4/security/ |
| D | Kconfig.hardening | 35 on the function calling complexity of a given workload's
131 are advised to test this feature on your expected workload before
179 workload, but most cases see <1% impact. Some synthetic
194 The performance impact varies by workload, but is more expensive
|
| /Linux-v5.4/Documentation/timers/ |
| 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,
212 but do not see any change in your workload's behavior. Is this because
213 your workload isn't affected that much by OS jitter, or is it because
224 possible, then you can conclude that your workload is not all that
300 constraining the workload. For example, the only way to eliminate
|
| /Linux-v5.4/drivers/gpu/drm/amd/powerplay/ |
| D | amdgpu_smu.c | 1608 long workload; in smu_adjust_power_state_dynamic() local
1653 workload = smu->workload_setting[index]; in smu_adjust_power_state_dynamic()
1655 if (smu->power_profile_mode != workload) in smu_adjust_power_state_dynamic()
1656 smu_set_power_profile_mode(smu, &workload, 0); in smu_adjust_power_state_dynamic()
1694 long workload; in smu_switch_power_profile() local
1709 workload = smu->workload_setting[index]; in smu_switch_power_profile()
1714 workload = smu->workload_setting[index]; in smu_switch_power_profile()
1718 smu_set_power_profile_mode(smu, &workload, 0); in smu_switch_power_profile()
|
| /Linux-v5.4/Documentation/accounting/ |
| D | psi.rst | 22 hardware according to workload demand.
30 workload health or risking major disruptions such as OOM kills.
52 actual CPU cycles are going to waste, and a workload that spends
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | kernel-per-CPU-kthreads.rst | 31 # run workload
230 1. Run your workload at a real-time priority, which will allow
270 slowly. Of course, you can also run your workload at
272 but if your workload is CPU-bound, this is a bad idea.
308 is feasible only if your workload never requires RCU priority
354 timer down to a level that is acceptable for your workload.
|
| /Linux-v5.4/block/ |
| D | Kconfig.iosched | 26 regardless of the device parameters and with any workload. It
|
| /Linux-v5.4/Documentation/block/ |
| D | bfq-iosched.rst | 84 Regardless of the actual background workload, BFQ guarantees that, for
100 until the background workload terminates (also on SSDs).
106 of the background I/O workload. As a consequence, these applications
107 do not suffer from almost any glitch due to the background workload.
112 If some additional workload happens to be executed in parallel, then
131 workload and regardless of the device parameters. From these bandwidth
248 workload and the budgets assigned to the queue.
347 So depending on storage and workload, it might be useful to set
370 throughput. One important case is random workload. Because of this
|
