public inbox for linux-arm-msm@vger.kernel.org
 help / color / mirror / Atom feed
From: Sharat Masetty <smasetty@codeaurora.org>
To: freedreno@lists.freedesktop.org
Cc: linux-arm-msm@vger.kernel.org,
	Sharat Masetty <smasetty@codeaurora.org>,
	dri-devel@lists.freedesktop.org
Subject: [PATCH 0/3] drm/msm: Revive GPU workload profiling
Date: Wed, 17 Oct 2018 18:33:58 +0530	[thread overview]
Message-ID: <1539781441-13076-1-git-send-email-smasetty@codeaurora.org> (raw)

I was looking for a simple mechanism to measure GPU workloads, it turns out
that the support is already present in the msm driver. In this series I try to
make use of the hardware counters where possible for a more accurate workload
estimation. Please review and share your thoughts on this.

I could have piggybacked on the devfreq samples and accumulated the busytimes,
but I chose not to, since it puts a dependency on the gpu devfreq which in
itself is an optional feature. There is one pending issue with GPU recovery +
sampling use case, which I plan to address soon.

Sharat Masetty (3):
  drm/msm: Change gpu_busy() function
  drm/msm/a6xx: Move power counter selectable to resume()
  drm/msm: Use Hardware counters for perf profiling

 drivers/gpu/drm/msm/adreno/a5xx_gpu.c |  6 +++---
 drivers/gpu/drm/msm/adreno/a6xx_gpu.c | 22 +++++++++++-----------
 drivers/gpu/drm/msm/msm_gpu.c         | 33 ++++++++++++++++++++++++++++-----
 drivers/gpu/drm/msm/msm_gpu.h         |  7 ++++---
 drivers/gpu/drm/msm/msm_perf.c        | 10 +++++-----
 5 files changed, 51 insertions(+), 27 deletions(-)

--
1.9.1

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2018-10-17 13:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-17 13:03 Sharat Masetty [this message]
     [not found] ` <1539781441-13076-1-git-send-email-smasetty-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-10-17 13:03   ` [PATCH 1/3] drm/msm: Change gpu_busy() function Sharat Masetty
     [not found]     ` <1539781441-13076-2-git-send-email-smasetty-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-10-17 14:39       ` Jordan Crouse
2018-10-17 13:04   ` [PATCH 2/3] drm/msm/a6xx: Move power counter selectable to resume() Sharat Masetty
     [not found]     ` <1539781441-13076-3-git-send-email-smasetty-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-10-17 14:09       ` Jordan Crouse
2018-10-17 13:04   ` [PATCH 3/3] drm/msm: Use Hardware counters for perf profiling Sharat Masetty
     [not found]     ` <1539781441-13076-4-git-send-email-smasetty-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-10-17 14:35       ` Jordan Crouse
     [not found]         ` <20181017143548.GD4751-9PYrDHPZ2Orvke4nUoYGnHL1okKdlPRT@public.gmane.org>
2018-10-26 13:46           ` Sharat Masetty
     [not found]             ` <f57bf8b2-c44a-68f5-a051-2a17c1ac5704-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-11-28 20:09               ` 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=1539781441-13076-1-git-send-email-smasetty@codeaurora.org \
    --to=smasetty@codeaurora.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=linux-arm-msm@vger.kernel.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