From: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
To: 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>,
Karunika Choo <karunika.choo@arm.com>
Cc: kernel@collabora.com, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/panthor: Add tracepoint for hardware utilisation changes
Date: Tue, 09 Dec 2025 14:01:23 +0100 [thread overview]
Message-ID: <3726594.R56niFO833@workhorse> (raw)
In-Reply-To: <4363e055-c1f9-49c6-81dd-c2e5f8307310@arm.com>
On Monday, 8 December 2025 18:14:53 Central European Standard Time Karunika Choo wrote:
> On 03/12/2025 13:56, Nicolas Frattaroli wrote:
> > [... snip ...]
> > diff --git a/drivers/gpu/drm/panthor/panthor_trace.h b/drivers/gpu/drm/panthor/panthor_trace.h
> > new file mode 100644
> > index 000000000000..01013f81e68a
> > --- /dev/null
> > +++ b/drivers/gpu/drm/panthor/panthor_trace.h
> > @@ -0,0 +1,38 @@
> > +/* SPDX-License-Identifier: GPL-2.0 or MIT */
> > +/* Copyright 2025 Collabora ltd. */
> > +
> > +#undef TRACE_SYSTEM
> > +#define TRACE_SYSTEM panthor
> > +
> > +#if !defined(__PANTHOR_TRACE_H__) || defined(TRACE_HEADER_MULTI_READ)
> > +#define __PANTHOR_TRACE_H__
> > +
> > +#include <linux/tracepoint.h>
> > +#include <linux/types.h>
> > +
> > +TRACE_EVENT(gpu_power_active,
> > + TP_PROTO(u64 shader_bitmap, u64 tiler_bitmap, u64 l2_bitmap),
>
> nit: if you want to add tracing can we also add the device name as
> well? Something like:
>
> TP_PROTO(struct device *dev, ...),
> TP_ARGS(dev, ...),
> TP_STRUCT__ENTRY(
> __string(dev_name, dev_name(dev))
> ...
> ).
> ...
This is a great idea, will do. Any specific reason to pass the
device in the tracepoint rather than a const char*?
>
> This will help differentiate the device it is originating from in
> a multi GPU situation.
I'll try not to get too excited at the prospect of systems using
multiple Mali GPUs because I know the likeliest case this happens
on is Arm evaluation systems with a hard IP and a soft IP loaded to
the FPGA core. :)
Kind regards,
Nicolas Frattaroli
>
> Kind regards,
> Karunika
>
> > + TP_ARGS(shader_bitmap, tiler_bitmap, l2_bitmap),
> > + TP_STRUCT__entry(
> > + __field(u64, shader_bitmap)
> > + __field(u64, tiler_bitmap)
> > + __field(u64, l2_bitmap)
> > + ),
> > + TP_fast_assign(
> > + __entry->shader_bitmap = shader_bitmap;
> > + __entry->tiler_bitmap = tiler_bitmap;
> > + __entry->l2_bitmap = l2_bitmap;
> > + ),
> > + TP_printk("shader_bitmap=0x%llx tiler_bitmap=0x%llx l2_bitmap=0x%llx",
> > + __entry->shader_bitmap, __entry->tiler_bitmap, __entry->l2_bitmap
> > + )
> > +);
> > +
> > +#endif /* __PANTHOR_TRACE_H__ */
> > +
> > +#undef TRACE_INCLUDE_PATH
> > +#define TRACE_INCLUDE_PATH .
> > +#undef TRACE_INCLUDE_FILE
> > +#define TRACE_INCLUDE_FILE panthor_trace
> > +
> > +#include <trace/define_trace.h>
> >
>
>
>
next prev parent reply other threads:[~2025-12-09 13:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 13:56 [PATCH 0/2] Add a few tracepoints to panthor Nicolas Frattaroli
2025-12-03 13:56 ` [PATCH 1/2] drm/panthor: Add tracepoint for hardware utilisation changes Nicolas Frattaroli
2025-12-04 20:21 ` Chia-I Wu
2025-12-05 10:47 ` Nicolas Frattaroli
2025-12-05 21:16 ` Chia-I Wu
2025-12-08 7:48 ` Nicolas Frattaroli
2025-12-08 18:28 ` Chia-I Wu
2025-12-09 10:32 ` Karunika Choo
2025-12-08 17:14 ` Karunika Choo
2025-12-09 13:01 ` Nicolas Frattaroli [this message]
2025-12-09 16:22 ` Karunika Choo
2025-12-09 17:10 ` Marcin Ślusarz
2025-12-08 17:21 ` Karunika Choo
2025-12-09 12:55 ` Nicolas Frattaroli
2025-12-03 13:56 ` [PATCH 2/2] drm/panthor: Add gpu_job_irq tracepoint Nicolas Frattaroli
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=3726594.R56niFO833@workhorse \
--to=nicolas.frattaroli@collabora.com \
--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=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