From: Steven Price <steven.price@arm.com>
To: "Adrián Larumbe" <adrian.larumbe@collabora.com>,
"Boris Brezillon" <boris.brezillon@collabora.com>,
"Rob Herring" <robh@kernel.org>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/1] Always record job cycle and timestamp information
Date: Wed, 14 Feb 2024 13:52:05 +0000 [thread overview]
Message-ID: <ba987da3-b4aa-410c-95ae-434e94793d85@arm.com> (raw)
In-Reply-To: <20240214121435.3813983-1-adrian.larumbe@collabora.com>
Hi Adrián,
On 14/02/2024 12:14, Adrián Larumbe wrote:
> A driver user expressed interest in being able to access engine usage stats
> through fdinfo when debugfs is not built into their kernel. In the current
> implementation, this wasn't possible, because it was assumed even for
> inflight jobs enabling the cycle counter and timestamp registers would
> incur in additional power consumption, so both were kept disabled until
> toggled through debugfs.
>
> A second read of the TRM made me think otherwise, but this is something
> that would be best clarified by someone from ARM's side.
I'm afraid I can't give a definitive answer. This will probably vary
depending on implementation. The command register enables/disables
"propagation" of the cycle/timestamp values. This propagation will cost
some power (gates are getting toggled) but whether that power is
completely in the noise of the GPU as a whole I can't say.
The out-of-tree kbase driver only enables the counters for jobs
explicitly marked (BASE_JD_REQ_PERMON) or due to an explicit connection
from a profiler.
I'd be happier moving the debugfs file to sysfs rather than assuming
that the power consumption is small enough for all platforms.
Ideally we'd have some sort of kernel interface for a profiler to inform
the kernel what it is interested in, but I can't immediately see how to
make that useful across different drivers. kbase's profiling support is
great with our profiling tools, but there's a very strong connection
between the two.
Steve
> Adrián Larumbe (1):
> drm/panfrost: Always record job cycle and timestamp information
>
> drivers/gpu/drm/panfrost/Makefile | 2 --
> drivers/gpu/drm/panfrost/panfrost_debugfs.c | 21 ------------------
> drivers/gpu/drm/panfrost/panfrost_debugfs.h | 14 ------------
> drivers/gpu/drm/panfrost/panfrost_device.h | 1 -
> drivers/gpu/drm/panfrost/panfrost_drv.c | 5 -----
> drivers/gpu/drm/panfrost/panfrost_job.c | 24 ++++++++-------------
> drivers/gpu/drm/panfrost/panfrost_job.h | 1 -
> 7 files changed, 9 insertions(+), 59 deletions(-)
> delete mode 100644 drivers/gpu/drm/panfrost/panfrost_debugfs.c
> delete mode 100644 drivers/gpu/drm/panfrost/panfrost_debugfs.h
>
>
> base-commit: 6b1f93ea345947c94bf3a7a6e668a2acfd310918
next prev parent reply other threads:[~2024-02-14 13:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 12:14 Adrián Larumbe
2024-02-14 12:14 ` [PATCH 1/1] drm/panfrost: " Adrián Larumbe
2024-02-14 13:52 ` Steven Price [this message]
2024-02-16 16:57 ` [PATCH 0/1] " Daniel Vetter
2024-02-16 17:43 ` Tvrtko Ursulin
2024-02-21 9:40 ` Adrián Larumbe
2024-02-21 14:34 ` Tvrtko Ursulin
2024-02-21 15:13 ` Adrián Larumbe
2024-02-28 14:13 ` Daniel Vetter
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=ba987da3-b4aa-410c-95ae-434e94793d85@arm.com \
--to=steven.price@arm.com \
--cc=adrian.larumbe@collabora.com \
--cc=airlied@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®