Lines Matching refs:submission
7 For upstream the overall plan for landing GuC submission and integrating the
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
22 * Bonding uAPI completely incompatible with GuC submission, plus it has
30 * Initially only for GuC submission but execlists can be supported if
33 * GuC submission backend fully integrated with DRM scheduler
45 features are not required for GuC submission as the GuC does
61 TODOs for GuC submission upstream
68 New uAPI for basic GuC submission
70 No major changes are required to the uAPI for basic GuC submission. The only
89 New parallel submission uAPI
91 The existing bonding uAPI is completely broken with GuC submission because
92 whether a submission is a single context submit or parallel submit isn't known
97 bonding uAPI does. Hence the need for a new parallel submission interface. Also
102 The new parallel submission uAPI consists of 3 parts:
106 submission
115 submission interface currently only supports submitting multiple contexts to
125 A 'set_parallel' extension to configure contexts for parallel submission
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
132 supports GuC submission. Execlists supports can be added later if needed.