From: Sharat Masetty <smasetty-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Cc: linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Sharat Masetty <smasetty-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [PATCH 0/4] Preemption support for A6xx targets
Date: Mon, 26 Feb 2018 13:08:19 +0530 [thread overview]
Message-ID: <1519630703-2957-1-git-send-email-smasetty@codeaurora.org> (raw)
This patch follows Jordan's recent "drm/msm: Add A6XX device support"
patch series and adds preemption support. Preemption allows the GPU to switch
to a higher priority ringbuffer when one is ready, thereby improving user
experience. A6xx hardware supports various preemption levels, each with
different granularities and different switch-out--switch-in times. While this
patch only enables the first preemption level i.e. preemption at the ringbuffer
level, support for more finer grained preemption levels will follow after
more testing.
Sharat Masetty (4):
drm/msm: Add submitqueue setup and close
drm/msm: Add new PM4 type7 opcodes
drm/msm/A6xx: Implement preemption for A6XX targets
drm/msm/A6xx: Enable preemption for A6xx targets
drivers/gpu/drm/msm/Makefile | 1 +
drivers/gpu/drm/msm/adreno/a6xx_gmu.c | 44 ++++
drivers/gpu/drm/msm/adreno/a6xx_gpu.c | 148 ++++++++++-
drivers/gpu/drm/msm/adreno/a6xx_gpu.h | 136 ++++++++++
drivers/gpu/drm/msm/adreno/a6xx_preempt.c | 383 ++++++++++++++++++++++++++++
drivers/gpu/drm/msm/adreno/adreno_pm4.xml.h | 2 +
drivers/gpu/drm/msm/msm_gpu.h | 7 +
drivers/gpu/drm/msm/msm_submitqueue.c | 15 +-
8 files changed, 731 insertions(+), 5 deletions(-)
create mode 100644 drivers/gpu/drm/msm/adreno/a6xx_preempt.c
--
1.9.1
_______________________________________________
Freedreno mailing list
Freedreno@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/freedreno
next reply other threads:[~2018-02-26 7:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 7:38 Sharat Masetty [this message]
[not found] ` <1519630703-2957-1-git-send-email-smasetty-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-02-26 7:38 ` [PATCH 1/4] drm/msm: Add submitqueue setup and close Sharat Masetty
[not found] ` <1519630703-2957-2-git-send-email-smasetty-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-04-03 21:19 ` Jordan Crouse
2018-02-26 7:38 ` [PATCH 2/4] drm/msm: Add new PM4 type7 opcodes Sharat Masetty
[not found] ` <1519630703-2957-3-git-send-email-smasetty-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-04-03 21:19 ` Jordan Crouse
2018-02-26 7:38 ` [PATCH 4/4] drm/msm/A6xx: Enable preemption for A6xx targets Sharat Masetty
[not found] ` <1519630703-2957-5-git-send-email-smasetty-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-04-03 21:19 ` Jordan Crouse
2018-02-26 7:38 ` [PATCH 3/4] drm/msm/A6xx: Implement preemption for A6XX targets Sharat Masetty
[not found] ` <1519630703-2957-4-git-send-email-smasetty-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-04-03 21:19 ` Jordan Crouse
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=1519630703-2957-1-git-send-email-smasetty@codeaurora.org \
--to=smasetty-sgv2jx0feol9jmxxk+q4oq@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=freedreno-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox