| /linux-6.3-rc2/Documentation/gpu/rfc/ |
| A D | i915_scheduler.rst | 10 * 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 …]
|
| A D | i915_vm_bind.rst | 12 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.3-rc2/drivers/gpu/drm/i915/gvt/ |
| A D | execlist.c | 373 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()
|
| A D | scheduler.c | 138 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()
740 struct intel_vgpu_submission *s = &vgpu->submission; in prepare_workload()
1050 struct intel_vgpu_submission *s = &vgpu->submission; in intel_vgpu_clean_workloads()
1072 struct intel_vgpu_submission *s = &vgpu->submission; in complete_current_workload()
1230 struct intel_vgpu_submission *s = &vgpu->submission; in intel_gvt_wait_vgpu_idle()
1320 struct intel_vgpu_submission *s = &vgpu->submission; in intel_vgpu_clean_submission()
1345 struct intel_vgpu_submission *s = &vgpu->submission; in intel_vgpu_reset_submission()
1385 struct intel_vgpu_submission *s = &vgpu->submission; in intel_vgpu_setup_submission()
[all …]
|
| A D | scheduler.h | 137 (&(vgpu)->submission.workload_q_head[(e)->id])
|
| A D | vgpu.c | 186 if (atomic_read(&vgpu->submission.running_workload_num)) { in intel_gvt_deactivate_vgpu()
281 INIT_LIST_HEAD(&vgpu->submission.workload_q_head[i]); in intel_gvt_create_idle_vgpu()
|
| A D | mmio_context.c | 357 struct intel_vgpu_submission *s = &vgpu->submission; in handle_tlb_pending_event()
512 s = &next->submission; in switch_mmio()
|
| /linux-6.3-rc2/Documentation/driver-api/surface_aggregator/ |
| A D | internal.rst | 175 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.3-rc2/Documentation/block/ |
| A D | null_blk.rst | 18 - Configurable submission queues per device.
68 The number of submission queues attached to the device driver. If unset, it
|
| A D | blk-mq.rst | 106 used by device drivers to map the device submission queues (or device DMA ring
107 buffer), and are the last step of the block layer submission code before the
|
| /linux-6.3-rc2/Documentation/usb/ |
| A D | usbmon.rst | 119 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.3-rc2/Documentation/maintainer/ |
| A D | maintainer-entry-profile.rst | 9 submission life-cycle. A contributor uses this document to level set
35 other maintainers in the submission chain.
|
| /linux-6.3-rc2/Documentation/process/ |
| A D | submit-checklist.rst | 3 Linux Kernel patch submission checklist
40 submission (``scripts/checkpatch.pl``).
|
| A D | stable-kernel-rules.rst | 79 changelog of your submission, as well as the kernel version you wish
142 Following the submission:
|
| /linux-6.3-rc2/drivers/gpu/drm/nouveau/ |
| A D | Kbuild | 60 # DRM - command submission
|
| /linux-6.3-rc2/tools/testing/selftests/net/forwarding/ |
| A D | README | 56 o Code shall be checked using ShellCheck [1] prior to submission.
|
| /linux-6.3-rc2/Documentation/driver-api/ |
| A D | dma-buf.rst | 220 been set. Used to asynchronously delay command submission.
242 Furthermore the kernel has to be able to hold up userspace command submission
275 * No DMA fences that signal end of batchbuffer for command submission where
302 compute side, like compute units or command submission engines. If both a 3D
|
| /linux-6.3-rc2/Documentation/gpu/ |
| A D | msm-crash-dump.rst | 72 List of buffers from the hanging submission if available.
|
| A D | drm-internals.rst | 18 management, command submission & fencing, suspend/resume support, and
249 command submission code. Do not use any of this in new and modern
|
| /linux-6.3-rc2/Documentation/sparc/oradax/ |
| A D | dax-hv-api.txt | 25 … 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 …]
|
| A D | oracle-dax.rst | 146 equal to the requested length, then the submission was completely
334 The CCB submission is a write() or pwrite() system call to the
344 After a successful submission of the CCB, the completion area may be
417 After the submission, the completion area polling code is identical to
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/ |
| A D | submitting-patches.rst | 10 0) Normal patch submission rules from
|
| /linux-6.3-rc2/Documentation/translations/zh_CN/process/ |
| A D | howto.rst | 113 "Linux kernel patch submission format"
|
| /linux-6.3-rc2/Documentation/translations/zh_TW/process/ |
| A D | howto.rst | 116 "Linux kernel patch submission format"
|
| /linux-6.3-rc2/Documentation/arc/ |
| A D | arc.rst | 19 where "work in progress" is hosted prior to submission to upstream projects.
|