From: Rob Clark <robdclark@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: freedreno@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
Jordan Crouse <jordan@cosmicpenguin.net>,
Akhil P Oommen <akhilpo@codeaurora.org>,
Rob Clark <robdclark@chromium.org>,
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH 0/2] drm/msm: Un-break multi-context gl
Date: Fri, 1 Oct 2021 10:58:54 -0700 [thread overview]
Message-ID: <20211001175857.1324712-1-robdclark@gmail.com> (raw)
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
next reply other threads:[~2021-10-01 17:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 17:58 Rob Clark [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211001175857.1324712-1-robdclark@gmail.com \
--to=robdclark@gmail.com \
--cc=akhilpo@codeaurora.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jordan@cosmicpenguin.net \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.