Home
last modified time | relevance | path

Searched refs:submission (Results 1 – 25 of 92) sorted by relevance

1234

/linux-6.15/Documentation/gpu/rfc/
H A Di915_scheduler.rst10 * Merge basic GuC submission
11 * Basic submission support for all gen11+ platforms
18 * Update IGTs / selftests as needed to work with GuC submission
20 * Rework / get CI heathly for GuC submission in place as needed
21 * Merge new parallel submission uAPI
33 * GuC submission backend fully integrated with DRM scheduler
61 TODOs for GuC submission upstream
68 New uAPI for basic GuC submission
89 New parallel submission uAPI
102 The new parallel submission uAPI consists of 3 parts:
[all …]
H A Di915_vm_bind.rst12 mappings during each submission (as required by older execbuf mode).
35 The i915 driver flushes the TLB for each submission and when an object's
56 works with execbuf3 ioctl for submission. All BOs mapped on that VM (through
58 submission.
81 During each execbuf submission, the request fence must be added to the
89 submission, they need only one dma-resv fence list updated. Thus, the fast
90 path (where required mappings are already bound) submission latency is O(1)
147 submission, they are added with DMA_RESV_USAGE_BOOKKEEP usage to prevent
/linux-6.15/Documentation/gpu/xe/
H A Dxe_cs.rst4 Command submission
8 :doc: Execbuf (User GPU command submission)
/linux-6.15/drivers/gpu/drm/i915/gvt/
H A Dexeclist.c373 struct intel_vgpu_submission *s = &vgpu->submission; in prepare_execlist_workload()
395 struct intel_vgpu_submission *s = &vgpu->submission; in complete_execlist_workload()
435 struct intel_vgpu_submission *s = &vgpu->submission; in submit_context()
459 struct intel_vgpu_submission *s = &vgpu->submission; in intel_vgpu_submit_execlist()
503 struct intel_vgpu_submission *s = &vgpu->submission; in init_vgpu_execlist()
525 struct intel_vgpu_submission *s = &vgpu->submission; in clean_execlist()
H A Dscheduler.c138 struct intel_vgpu_submission *s = &vgpu->submission; in populate_shadow_context()
462 struct intel_vgpu_submission *s = &vgpu->submission; in intel_gvt_workload_req_alloc()
489 struct intel_vgpu_submission *s = &vgpu->submission; in intel_gvt_scan_and_shadow_workload()
741 struct intel_vgpu_submission *s = &vgpu->submission; in prepare_workload()
1051 struct intel_vgpu_submission *s = &vgpu->submission; in intel_vgpu_clean_workloads()
1073 struct intel_vgpu_submission *s = &vgpu->submission; in complete_current_workload()
1231 struct intel_vgpu_submission *s = &vgpu->submission; in intel_gvt_wait_vgpu_idle()
1321 struct intel_vgpu_submission *s = &vgpu->submission; in intel_vgpu_clean_submission()
1346 struct intel_vgpu_submission *s = &vgpu->submission; in intel_vgpu_reset_submission()
1386 struct intel_vgpu_submission *s = &vgpu->submission; in intel_vgpu_setup_submission()
[all …]
H A Dscheduler.h135 (&(vgpu)->submission.workload_q_head[(e)->id])
H A Dvgpu.c187 if (atomic_read(&vgpu->submission.running_workload_num)) { in intel_gvt_deactivate_vgpu()
282 INIT_LIST_HEAD(&vgpu->submission.workload_q_head[i]); in intel_gvt_create_idle_vgpu()
H A Dmmio_context.c365 struct intel_vgpu_submission *s = &vgpu->submission; in handle_tlb_pending_event()
520 s = &next->submission; in switch_mmio()
/linux-6.15/Documentation/gpu/
H A Dmsm-preemption.rst23 submission occurs the kernel finds the highest priority ring which isn't empty
25 also done whenever a submission completes to make sure execution resumes on a
40 Preemption only occurs at the submission level. This requires the least amount
H A Dnouveau.rst19 submission required for the proper functioning of NVIDIA GPUs under the
H A Dmsm-crash-dump.rst72 List of buffers from the hanging submission if available.
H A Ddrm-internals.rst18 management, command submission & fencing, suspend/resume support, and
226 command submission code. Do not use any of this in new and modern
/linux-6.15/Documentation/driver-api/surface_aggregator/
H A Dinternal.rst175 re-submission, packets are not removed from the pending set.
187 this submission, the packet is completed by the transmitter thread with the
209 well as initiating re-submission of all currently pending packets on
210 receival of a NAK message (re-submission in case of a NAK is similar to
225 thread). It is used to trigger re-submission or, when the number of tries
236 ``-ETIMEDOUT`` as status if not. Note that re-submission, in this case and
255 In addition to guarding the collections, after initial packet submission
270 submission, i.e. cancellation, can not rely on the ``ptl`` reference to be
279 With respect to the interface for higher layers, packet submission
283 submission may not run concurrently with itself for the same packet.
[all …]
/linux-6.15/Documentation/block/
H A Dnull_blk.rst18 - Configurable submission queues per device.
68 The number of submission queues attached to the device driver. If unset, it
/linux-6.15/Documentation/usb/
H A Dusbmon.rst119 Any text format data consists of a stream of events, such as URB submission,
120 URB callback, submission error. Every event is a text line, which consists
135 Available types are: S - submission, C - callback, E - submission error.
163 In case of a submission of a Control packet, this field contains a Setup Tag
219 u64 id; /* 0: URB ID - from submission to callback */
/linux-6.15/Documentation/devicetree/bindings/
H A Dsubmitting-patches.rst10 0) Normal patch submission rules from
66 bindings submission on the mailing list.
/linux-6.15/Documentation/process/
H A Dsubmit-checklist.rst4 Linux Kernel patch submission checklist
67 submission (``scripts/checkpatch.pl``).
H A Dstable-kernel-rules.rst55 at the time of submission. :ref:`option_3` is an alternative to the two earlier
156 submission with a separate line above the commit text, like this::
169 Following the submission
/linux-6.15/Documentation/maintainer/
H A Dmaintainer-entry-profile.rst9 submission life-cycle. A contributor uses this document to level set
35 other maintainers in the submission chain.
/linux-6.15/Documentation/nvme/
H A Dnvme-pci-endpoint-target.rst32 1) The driver manages retrieval of NVMe commands in submission queues using DMA
36 constantly poll the doorbell of all submission queues to detect command
81 The driver also implements IRQ vector coalescing and submission queue
131 not support multiple submission queues using the same completion queue. All
132 submission queues must specify a unique completion queue.
/linux-6.15/drivers/gpu/drm/nouveau/
H A DKbuild60 # DRM - command submission
/linux-6.15/Documentation/driver-api/
H A Ddma-buf.rst248 been set. Used to asynchronously delay command submission.
270 Furthermore the kernel has to be able to hold up userspace command submission
303 * No DMA fences that signal end of batchbuffer for command submission where
330 compute side, like compute units or command submission engines. If both a 3D
/linux-6.15/Documentation/arch/sparc/oradax/
H A Ddax-hv-api.txt25 … compatibility property. Functionality is accessed through the submission of Command Control Blocks
42 not be a guarantee that a future submission would succeed.
132 via the ccb_kill API call. Changes in virtual address mappings occurring after CCB submission are n…
208 CCB submission. CCBs without the Serial flag set execute independently, even if they are between CC…
239 …will result in the CCB submission being rejected, with the causal virtual address indicated. The C…
1026 successfully. All other fields are considered invalid upon CCB submission until the CCB execution s…
1210 … and no errors were been encountered during submission. Some submitted
1231 or TSB contents. The submission may be retried after adding the required
1238 EINVAL The virtual machine detected an invalid CCB during submission, or invalid
1240 will be detected during submission, and some may be reported as errors in the
[all …]
/linux-6.15/Documentation/translations/ja_JP/process/
H A Dhowto.rst138 "Linux kernel patch submission format"
/linux-6.15/tools/testing/selftests/net/forwarding/
H A DREADME56 o Code shall be checked using ShellCheck [1] prior to submission.

1234