From: Sasha Levin <sashal@kernel.org>
To: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
Cc: Boris Brezillon <boris.brezillon@collabora.com>,
Steven Price <steven.price@arm.com>,
Liviu Dudau <liviu.dudau@arm.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Chia-I Wu <olvaffe@gmail.com>,
Karunika Choo <karunika.choo@arm.com>,
kernel@collabora.com, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v10 3/4] drm/panthor: Add tracepoint for hardware utilisation changes
Date: Thu, 22 Jan 2026 23:02:21 -0500 [thread overview]
Message-ID: <aXLyzd6pMmexwWlY@laps> (raw)
In-Reply-To: <20260116-panthor-tracepoints-v10-3-d925986e3d1b@collabora.com>
Hi Nicolas,
On Fri, Jan 16, 2026 at 01:57:32PM +0100, Nicolas Frattaroli wrote:
>Mali GPUs have three registers that indicate which parts of the hardware
>are powered at any moment. These take the form of bitmaps. In the case
>of SHADER_READY for example, a high bit indicates that the shader core
>corresponding to that bit index is powered on. These bitmaps aren't
>solely contiguous bits, as it's common to have holes in the sequence of
>shader core indices, and the actual set of which cores are present is
>defined by the "shader present" register.
>
>When the GPU finishes a power state transition, it fires a
>GPU_IRQ_POWER_CHANGED_ALL interrupt. After such an interrupt is
>received, the _READY registers will contain new interesting data. During
>power transitions, the GPU_IRQ_POWER_CHANGED interrupt will fire, and
>the registers will likewise contain potentially changed data.
>
>This is not to be confused with the PWR_IRQ_POWER_CHANGED_ALL interrupt,
>which is something related to Mali v14+'s power control logic. The
>_READY registers and corresponding interrupts are already available in
>v9 and onwards.
>
>Expose the data as a tracepoint to userspace. This allows users to debug
>various scenarios and gather interesting information, such as: knowing
>how much hardware is lit up at any given time, correlating graphics
>corruption with a specific powered shader core, measuring when hardware
>is allowed to go to a powered off state again, and so on.
>
>The registration/unregistration functions for the tracepoint go through
>a wrapper in panthor_hw.c, so that v14+ can implement the same
>tracepoint by adding its hardware specific IRQ on/off callbacks to the
>panthor_hw.ops member.
>
>Signed-off-by: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
>---
> drivers/gpu/drm/panthor/panthor_gpu.c | 28 +++++++++++++++
> drivers/gpu/drm/panthor/panthor_gpu.h | 2 ++
> drivers/gpu/drm/panthor/panthor_hw.c | 62 +++++++++++++++++++++++++++++++++
> drivers/gpu/drm/panthor/panthor_hw.h | 8 +++++
> drivers/gpu/drm/panthor/panthor_trace.h | 58 ++++++++++++++++++++++++++++++
> 5 files changed, 158 insertions(+)
>
>diff --git a/drivers/gpu/drm/panthor/panthor_gpu.c b/drivers/gpu/drm/panthor/panthor_gpu.c
>index 9304469a711a..2ab444ee8c71 100644
>--- a/drivers/gpu/drm/panthor/panthor_gpu.c
>+++ b/drivers/gpu/drm/panthor/panthor_gpu.c
>@@ -22,6 +22,9 @@
> #include "panthor_hw.h"
> #include "panthor_regs.h"
>
>+#define CREATE_TRACE_POINTS
>+#include "panthor_trace.h"
With this commit, I'm seeing:
In file included from drivers/gpu/drm/panthor/panthor_trace.h:86,
from drivers/gpu/drm/panthor/panthor_gpu.c:26:
./include/trace/define_trace.h:118:42: fatal error: ./panthor_trace.h: No such file or directory
118 | #include TRACE_INCLUDE(TRACE_INCLUDE_FILE)
I think we need to add in 'CFLAGS_panthor_gpu.o := -I$(src)' to the Makefile
too, but I haven't tested that yet.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-01-23 4:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 12:57 [PATCH v10 0/4] Add a few tracepoints to panthor Nicolas Frattaroli
2026-01-16 12:57 ` [PATCH v10 1/4] drm/panthor: Rework panthor_irq::suspended into panthor_irq::state Nicolas Frattaroli
2026-01-16 13:21 ` Boris Brezillon
2026-01-16 15:55 ` Steven Price
2026-01-16 12:57 ` [PATCH v10 2/4] drm/panthor: Extend IRQ helpers for mask modification/restoration Nicolas Frattaroli
2026-01-16 13:41 ` Boris Brezillon
2026-01-16 14:41 ` Nicolas Frattaroli
2026-01-16 15:06 ` Boris Brezillon
2026-01-16 15:56 ` Steven Price
2026-01-16 12:57 ` [PATCH v10 3/4] drm/panthor: Add tracepoint for hardware utilisation changes Nicolas Frattaroli
2026-01-16 13:59 ` Boris Brezillon
2026-01-16 15:56 ` Steven Price
2026-01-23 4:02 ` Sasha Levin [this message]
2026-01-23 12:52 ` Nicolas Frattaroli
2026-01-23 19:45 ` Nathan Chancellor
2026-01-16 12:57 ` [PATCH v10 4/4] drm/panthor: Add gpu_job_irq tracepoint Nicolas Frattaroli
2026-01-16 14:00 ` Boris Brezillon
2026-01-16 15:56 ` Steven Price
2026-01-22 14:40 ` [PATCH v10 0/4] Add a few tracepoints to panthor Boris Brezillon
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=aXLyzd6pMmexwWlY@laps \
--to=sashal@kernel.org \
--cc=airlied@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=karunika.choo@arm.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nicolas.frattaroli@collabora.com \
--cc=olvaffe@gmail.com \
--cc=simona@ffwll.ch \
--cc=steven.price@arm.com \
--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