gpu/rfc/i915_scheduler.rst

21 * Merge new parallel submission uAPI
38 		* Lots of complexity of the GuC backend can be pulled out once
54 	* Remove in-order completion assumptions from DRM scheduler
57 		  finish out of order
58 	* Pull out i915 priority levels and use DRM priority levels
75 * -1k to -1 Low priority
84 ----------------
86 * https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/chap5.html#devsandqueues-priori…
87 * https://spec.oneapi.com/level-zero/latest/core/api.html#ze-command-queue-priority-t
89 New parallel submission uAPI
92 whether a submission is a single context submit or parallel submit isn't known
94 contexts in parallel with the GuC the context must be explicitly registered with
97 bonding uAPI does. Hence the need for a new parallel submission interface. Also
102 The new parallel submission uAPI consists of 3 parts:
105 * A 'set_parallel' extension to configure contexts for parallel
110 ------------------------------
112 (e.g. split-frame on gen11+). The logical mapping of engine instances can change
125 A 'set_parallel' extension to configure contexts for parallel submission
126 ------------------------------------------------------------------------
127 The 'set_parallel' extension configures a slot for parallel submission of N BBs.
130 similar existing examples. Once a slot is configured for parallel submission the
138 .. c:namespace-push:: rfc
140 .. kernel-doc:: include/uapi/drm/i915_drm.h
143 .. c:namespace-pop::
146 -------------------------------------------------------------------