From: Boris Brezillon <boris.brezillon@collabora.com>
To: Lukas Zapolskas <lukas.zapolskas@arm.com>
Cc: "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>,
"Adrián Larumbe" <adrian.larumbe@collabora.com>,
nd@arm.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
"Mihail Atanassov" <mihail.atanassov@arm.com>
Subject: Re: [PATCH v6 5/7] drm/panthor: Implement the counter sampler and sample handling
Date: Tue, 13 Jan 2026 17:19:07 +0100 [thread overview]
Message-ID: <20260113171907.02623198@fedora> (raw)
In-Reply-To: <20251215171453.2506348-6-lukas.zapolskas@arm.com>
On Mon, 15 Dec 2025 17:14:51 +0000
Lukas Zapolskas <lukas.zapolskas@arm.com> wrote:
> +#define BLK_MASK(x) GENMASK_ULL((x) - 1, 0)
> +
> +static u64 get_sc_mask(struct panthor_device *ptdev)
> +{
> + const u64 sc_mask = ptdev->gpu_info.shader_present;
Hm, so I've just merged a change to allow overriding this
shader_present with a value loaded from an nvmem cell, meaning the
value returned to userspace no longer matches the number of cores known
by the GPU. I have a local hack to apply such overrides late and keep
panthor_device::gpu_info as the HW state, but this forces us to
be careful about which variant of shader_present we want depending on
the context (in panthor_{fw,sched}.c we want the user value, in
panthor_perf.c, it we want the user value in get_sc_mask(), and the HW
value in get_reserved_sc_blocks()).
> +
> + return BLK_MASK(hweight64(sc_mask));
I believe this should be sc_mask on v13-, and
BLK_MASK(hweight64(sc_mask)) on v14+.
> +}
next prev parent reply other threads:[~2026-01-13 16:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 17:14 [PATCH v6 0/7] Performance counter implementation with single manual client support Lukas Zapolskas
2025-12-15 17:14 ` [PATCH v6 1/7] drm/panthor: Add performance counter uAPI Lukas Zapolskas
2025-12-16 10:59 ` Boris Brezillon
2025-12-16 17:30 ` Boris Brezillon
2026-01-07 15:14 ` Lukas Zapolskas
2025-12-17 14:37 ` Boris Brezillon
2026-01-07 15:13 ` Lukas Zapolskas
2026-01-07 15:32 ` Boris Brezillon
2025-12-22 18:15 ` kernel test robot
2026-01-14 13:06 ` Boris Brezillon
2025-12-15 17:14 ` [PATCH v6 2/7] drm/panthor: Add DEV_QUERY.PERF_INFO handling for Gx10 Lukas Zapolskas
2026-01-14 10:11 ` Boris Brezillon
2025-12-15 17:14 ` [PATCH v6 3/7] drm/panthor: Add panthor perf initialization and termination Lukas Zapolskas
2025-12-18 10:33 ` Boris Brezillon
2025-12-18 10:37 ` Boris Brezillon
2025-12-18 13:30 ` Boris Brezillon
2025-12-15 17:14 ` [PATCH v6 4/7] drm/panthor: Introduce sampling sessions to handle userspace clients Lukas Zapolskas
2026-01-14 12:07 ` Boris Brezillon
2025-12-15 17:14 ` [PATCH v6 5/7] drm/panthor: Implement the counter sampler and sample handling Lukas Zapolskas
2025-12-20 14:34 ` kernel test robot
2025-12-21 5:13 ` kernel test robot
2026-01-13 16:19 ` Boris Brezillon [this message]
2025-12-15 17:14 ` [PATCH v6 6/7] drm/panthor: Add suspend, resume and reset handling Lukas Zapolskas
2025-12-15 17:14 ` [PATCH v6 7/7] drm/panthor: Expose the panthor perf ioctls Lukas Zapolskas
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=20260113171907.02623198@fedora \
--to=boris.brezillon@collabora.com \
--cc=adrian.larumbe@collabora.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=lukas.zapolskas@arm.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mihail.atanassov@arm.com \
--cc=mripard@kernel.org \
--cc=nd@arm.com \
--cc=simona@ffwll.ch \
--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