Home
last modified time | relevance | path

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

12345

/linux-6.6.21/drivers/gpu/drm/i915/gvt/
Dscheduler.c63 static void update_shadow_pdps(struct intel_vgpu_workload *workload) in update_shadow_pdps() argument
66 struct intel_context *ctx = workload->req->context; in update_shadow_pdps()
68 if (WARN_ON(!workload->shadow_mm)) in update_shadow_pdps()
71 if (WARN_ON(!atomic_read(&workload->shadow_mm->pincount))) in update_shadow_pdps()
76 (void *)workload->shadow_mm->ppgtt_mm.shadow_pdps); in update_shadow_pdps()
84 static void sr_oa_regs(struct intel_vgpu_workload *workload, in sr_oa_regs() argument
87 struct drm_i915_private *dev_priv = workload->vgpu->gvt->gt->i915; in sr_oa_regs()
101 if (workload->engine->id != RCS0) in sr_oa_regs()
105 workload->oactxctrl = reg_state[ctx_oactxctrl + 1]; in sr_oa_regs()
107 for (i = 0; i < ARRAY_SIZE(workload->flex_mmio); i++) { in sr_oa_regs()
[all …]
Dexeclist.c370 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 …]
Dcmd_parser.c515 struct intel_vgpu_workload *workload; member
853 u32 base = s->workload->engine->mmio_base; in is_cmd_update_pdps()
861 struct intel_vgpu_mm *shadow_mm = s->workload->shadow_mm; in cmd_pdp_mmio_update_handler()
877 &s->workload->lri_shadow_mm); in cmd_pdp_mmio_update_handler()
1017 s->workload->ring_context_gpa + 12, &ctx_sr_ctl, 4); in cmd_reg_handler()
1228 s->workload->pending_events); in cmd_handler_pipe_control()
1235 s->workload->pending_events); in cmd_handler_mi_user_interrupt()
1748 s->workload->pending_events); in cmd_handler_mi_flush_dw()
1819 s->vgpu->gtt.ggtt_mm : s->workload->shadow_mm; in find_bb_size()
1835 s->engine->name, s->workload); in find_bb_size()
[all …]
Dcmd_parser.h50 int intel_gvt_scan_and_shadow_ringbuffer(struct intel_vgpu_workload *workload);
56 int intel_gvt_scan_engine_context(struct intel_vgpu_workload *workload);
Dtrace.h231 void *workload, const char *cmd_name),
234 buf_addr_type, workload, cmd_name),
243 __field(void*, workload)
255 __entry->workload = workload;
271 __entry->workload)
Dscheduler.h139 void intel_vgpu_queue_workload(struct intel_vgpu_workload *workload);
166 void intel_vgpu_destroy_workload(struct intel_vgpu_workload *workload);
/linux-6.6.21/Documentation/admin-guide/
Dworkload-tracing.rst4 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-6.6.21/tools/perf/tests/
Dperf-record.c114 err = sched__get_first_possible_cpu(evlist->workload.pid, &cpu_mask); in test__PERF_RECORD()
126 if (sched_setaffinity(evlist->workload.pid, cpu_mask_size, &cpu_mask) < 0) { in test__PERF_RECORD()
212 if ((pid_t)sample.pid != evlist->workload.pid) { in test__PERF_RECORD()
214 name, evlist->workload.pid, sample.pid); in test__PERF_RECORD()
218 if ((pid_t)sample.tid != evlist->workload.pid) { in test__PERF_RECORD()
220 name, evlist->workload.pid, sample.tid); in test__PERF_RECORD()
229 (pid_t)event->comm.pid != evlist->workload.pid) { in test__PERF_RECORD()
Dbuiltin-test.c522 const char *workload = NULL; in cmd_test() local
529 OPT_STRING('w', "workload", &workload, "work", "workload to run for testing"), in cmd_test()
547 if (workload) in cmd_test()
548 return run_workload(workload, argc, argv); in cmd_test()
/linux-6.6.21/Documentation/accel/qaic/
Daic100.rst66 with the QSM. Except for workload data via the DMA Bridge, all interaction with
82 (Q6) DSP with HVX and HMX. Each NSP can only run one workload at a time, but
83 multiple NSPs may be assigned to a single workload. Since each NSP can only run
84 one workload, AIC100 is limited to 16 concurrent workloads. Workload
94 workload is assigned a single DMA Bridge channel. The DMA Bridge exposes
117 1. Compile the workload into an ELF targeting the NSP(s)
118 2. Make requests to the QSM to load the workload and related artifacts into the
120 3. Make a request to the QSM to activate the workload onto a set of idle NSPs
121 4. Make requests to the DMA Bridge to send input data to the workload to be
123 workload.
[all …]
Dqaic.rst15 if the workload is particularly quick, and the host is responsive. If the host
19 workload's ability to process inputs. The lprnet (license plate reader network)
20 workload is known to trigger this condition, and can generate in excess of 100k
29 sleep for a time to see if the workload will generate more activity. The IRQ
36 workload throughput performance (within run to run noise variation).
82 or receive data from a workload. The call will return a GEM handle that
93 get sent where to a workload. This requires a set of DMA transfers for the
132 workload should be allowed to interface with the DBC.
/linux-6.6.21/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
/linux-6.6.21/Documentation/admin-guide/mm/
Didle_page_tracking.rst9 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-6.6.21/tools/perf/tests/shell/
Dstat_metrics_values.sh20 workload="perf bench futex hash -r 2 -s"
25 $PYTHON $pythonvalidator -rule $rulefile -output_dir $tmpdir -wl "${workload}"
Dtest_intel_pt.sh23 workload="${temp_dir}/workload"
63 cat << _end_of_file_ | /usr/bin/cc -o "${workload}" -xc - -pthread && have_workload=true
254 $workload &
256 $workload &
/linux-6.6.21/tools/perf/tests/shell/lib/
Dperf_metric_validation.py10 …name, reportfname='', t=5, debug=False, datafname='', fullrulefname='', workload='true', metrics='… argument
19 self.workloads = [x for x in workload.split(",") if x]
360 def _run_perf(self, metric, workload: str):
363 wl = workload.split()
371 def collect_perf(self, workload: str):
392 else: wl = workload
400 workload = self.workloads[self.wlidx]
402 data = self._run_perf(metric, workload)
562 datafname=datafile, fullrulefname=fullrule, workload=args.wl,
/linux-6.6.21/tools/perf/bench/
Dfind-bit-bench.c34 static noinline void workload(int val) in workload() function
82 workload(bit); in do_for_each_set_bit()
97 workload(bit); in do_for_each_set_bit()
/linux-6.6.21/Documentation/filesystems/nfs/
Dknfsd-stats.rst54 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-6.6.21/drivers/gpu/drm/amd/pm/powerplay/hwmgr/
Dpp_psm.c272 long workload; in psm_adjust_power_state_dynamic() local
297 workload = hwmgr->workload_setting[index]; in psm_adjust_power_state_dynamic()
299 if (hwmgr->power_profile_mode != workload && hwmgr->hwmgr_func->set_power_profile_mode) in psm_adjust_power_state_dynamic()
300 hwmgr->hwmgr_func->set_power_profile_mode(hwmgr, &workload, 0); in psm_adjust_power_state_dynamic()
/linux-6.6.21/Documentation/tools/rtla/
Dcommon_timerlat_options.rst32 Set timerlat to run without a workload, and then dispatches user-space workloads
33 to wait on the timerlat_fd. Once the workload is awakes, it goes to sleep again
/linux-6.6.21/Documentation/scheduler/
Dsched-capacity.rst72 With a workload that periodically does a fixed amount of work, you will get an
103 Executing the same workload as described in 1.3.1, which each CPU running at its
111 workload on CPU1
151 One issue that needs to be taken into account is that a workload's duty cycle is
153 periodic workload at a given frequency F::
162 Now, consider running the *same* workload at frequency F/2::
184 identical workload on CPUs of different capacity values will yield different
192 Executing a given periodic workload on each CPU at their maximum frequency would
383 workload on CPU0
390 workload on CPU1
[all …]
/linux-6.6.21/Documentation/admin-guide/mm/damon/
Dstart.rst50 with your real workload. The last line asks ``damo`` to record the access
123 >=60 seconds in your workload to be swapped out. ::
127 <pid of your workload>
/linux-6.6.21/Documentation/translations/zh_CN/scheduler/
Dsched-capacity.rst108 workload on CPU1
339 workload on CPU0
346 workload on CPU1
/linux-6.6.21/Documentation/admin-guide/pm/
Dintel-speed-select.rst10 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-6.6.21/Documentation/timers/
Dno_hz.rst52 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,
206 but do not see any change in your workload's behavior. Is this because
207 your workload isn't affected that much by OS jitter, or is it because
218 possible, then you can conclude that your workload is not all that
294 constraining the workload. For example, the only way to eliminate

12345