linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH 0/2] drm/msm: Un-break multi-context gl
@ 2021-10-01 17:58 Rob Clark
  2021-10-01 17:58 ` [PATCH 1/2] drm/msm: A bit more docs + cleanup Rob Clark
  2021-10-01 17:58 ` [PATCH 2/2] drm/msm: One sched entity per process per priority Rob Clark
  0 siblings, 2 replies; 3+ messages in thread
From: Rob Clark @ 2021-10-01 17:58 UTC (permalink / raw)
  To: dri-devel
  Cc: freedreno, linux-arm-msm, Jordan Crouse, Akhil P Oommen,
	Rob Clark, open list

From: Rob Clark <robdclark@chromium.org>

Userspace is expecting that a single thread doing rendering against
multiple contexts does not need additional synchronization between those
contexts beyond ensuring work is flushed to the kernel in the correct
order.  But if we have a sched-entity per-context, and are not using
implicit sync, GPU jobs from different contexts can execute in a
different order than they were flushed to the kernel.

To solve that, share sched-entities for a given priority level between
submitqueues (which map to gl contexts).

Rob Clark (2):
  drm/msm: A bit more docs + cleanup
  drm/msm: One sched entity per process per priority

 drivers/gpu/drm/msm/msm_drv.h         | 44 -----------------
 drivers/gpu/drm/msm/msm_gem_submit.c  |  2 +-
 drivers/gpu/drm/msm/msm_gpu.h         | 66 +++++++++++++++++++++++++-
 drivers/gpu/drm/msm/msm_submitqueue.c | 68 +++++++++++++++++++++++----
 4 files changed, 123 insertions(+), 57 deletions(-)

-- 
2.31.1


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-10-01 17:54 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-10-01 17:58 [PATCH 0/2] drm/msm: Un-break multi-context gl Rob Clark
2021-10-01 17:58 ` [PATCH 1/2] drm/msm: A bit more docs + cleanup Rob Clark
2021-10-01 17:58 ` [PATCH 2/2] drm/msm: One sched entity per process per priority Rob Clark

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).