[PATCH 1/8] drm/i915: Move priolist to new i915_sched_engine object

2021-06-17 Thread Matthew Brost
Introduce i915_sched_engine object which is lower level data structure that i915_scheduler / generic code can operate on without touching execlist specific structures. This allows additional submission backends to be added without breaking the layering. Currently the execlists backend uses 1 of

[PATCH 1/8] drm/i915: Move priolist to new i915_sched_engine object

2021-06-15 Thread Matthew Brost
Introduce i915_sched_engine object which is lower level data structure that i915_scheduler / generic code can operate on without touching execlist specific structures. This allows additional submission backends to be added without breaking the layering. Currently the execlists backend uses 1 of

[PATCH 1/8] drm/i915: Move priolist to new i915_sched_engine object

2021-06-15 Thread Matthew Brost
Introduce i915_sched_engine object which is lower level data structure that i915_scheduler / generic code can operate on without touching execlist specific structures. This allows additional submission backends to be added without breaking the layering. Currently the execlists backend uses 1 of

Re: [PATCH 1/8] drm/i915: Move priolist to new i915_sched_engine object

2021-06-14 Thread Daniele Ceraolo Spurio
On 6/8/2021 12:17 PM, Matthew Brost wrote: Introduce i915_sched_engine object which is lower level data structure that i915_scheduler / generic code can operate on without touching execlist specific structures. This allows additional submission backends to be added without breaking the

[PATCH 1/8] drm/i915: Move priolist to new i915_sched_engine object

2021-06-08 Thread Matthew Brost
Introduce i915_sched_engine object which is lower level data structure that i915_scheduler / generic code can operate on without touching execlist specific structures. This allows additional submission backends to be added without breaking the layering. This is a bit of detour to integrating the