Rob Clark 68002469e5 drm/msm: One sched entity per process per priority ... Some userspace apps make assumptions that rendering against multiple contexts within the same process (from the same thread, with appropriate MakeCurrent() calls) provides sufficient synchronization without any external synchronization (ie. glFenceSync()/glWaitSync()). Since a submitqueue maps to a gl/vk context, having multiple sched entities of the same priority only works with implicit sync enabled. To fix this, limit things to a single sched entity per priority level per process. An alternative would be sharing submitqueues between contexts in userspace, but tracking of per-context faults (ie. GL_EXT_robustness) is already done at the submitqueue level, so this is not an option. Signed-off-by: Rob Clark <robdclark@chromium.org>		2021-10-01 13:13:19 -07:00
..
drm	drm/msm: One sched entity per process per priority	2021-10-01 13:13:19 -07:00
host1x	gpu: host1x: debug: Dump DMASTART and DMAEND register	2021-08-13 18:23:32 +02:00
ipu-v3	Updates to the interrupt core and driver subsystems:	2021-08-30 14:38:37 -07:00
trace
vga	vgaarb: don't pass a cookie to vga_client_register	2021-07-21 10:29:10 +02:00
Makefile