From: "Adrián Larumbe" <adrian.larumbe@collabora.com>
To: linux-kernel@vger.kernel.org
Cc: dri-devel@lists.freedesktop.org,
"Steven Price" <steven.price@arm.com>,
"Boris Brezillon" <boris.brezillon@collabora.com>,
kernel@collabora.com,
"Adrián Larumbe" <adrian.larumbe@collabora.com>
Subject: [PATCH v3 0/4] Introduce Panfrost JM contexts
Date: Fri, 12 Sep 2025 14:19:11 +0100 [thread overview]
Message-ID: <20250912132002.304187-1-adrian.larumbe@collabora.com> (raw)
This patch series brings the notion of JM contexts into Panfrost.
UM will be able to create contexts, get a handle for them and attach
it to a job submission. Contexts describe basic HW resource assignment
to jobs, but at the moment that includes priorities only.
There's a MR for a Mesa commit series that makes use of these changes:
https://lore.kernel.org/dri-devel/20250904001054.147465-1-adrian.larumbe@collabora.com/
Changelog:
v3:
- Cut down number of available contexts per file to 64.
- Conservatively restored JS thread priority back to 8.
- Rework of the context destruction and scheduler entity release
logic to avoid races and that no new jobs are run after ctx destruction.
- Refactor privilege checks when allowing high context priorities.
- Checked that uapi struct padding fields are zeroed in ioctls
v2:
- Core and L2 cache affinities are not longer part of the context uAPI
- Individual JS priorites are no longer possible, and the same context
priority is applied onto all the JS and scheduler entities.
- Minor changes in the debugfs knob to reflect all the above.
Boris Brezillon (4):
drm/panfrost: Introduce uAPI for JM context creation
drm/panfrost: Introduce JM contexts for manging job resources
drm/panfrost: Expose JM context IOCTLs to UM
drm/panfrost: Display list of device JM contexts over debugfs
drivers/gpu/drm/panfrost/panfrost_device.h | 11 +-
drivers/gpu/drm/panfrost/panfrost_drv.c | 150 +++++++++++++++-
drivers/gpu/drm/panfrost/panfrost_job.c | 195 +++++++++++++++++----
drivers/gpu/drm/panfrost/panfrost_job.h | 25 ++-
include/uapi/drm/panfrost_drm.h | 50 ++++++
5 files changed, 391 insertions(+), 40 deletions(-)
base-commit: a3ae3384be7704fcf41279f13190bd8a11204bea
--
2.51.0
next reply other threads:[~2025-09-12 13:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 13:19 Adrián Larumbe [this message]
2025-09-12 13:19 ` [PATCH v3 1/4] drm/panfrost: Introduce uAPI for JM context creation Adrián Larumbe
2025-09-12 13:19 ` [PATCH v3 2/4] drm/panfrost: Introduce JM contexts for manging job resources Adrián Larumbe
2025-09-17 10:15 ` Steven Price
2025-09-17 12:15 ` Adrián Larumbe
2025-09-12 13:19 ` [PATCH v3 3/4] drm/panfrost: Expose JM context IOCTLs to UM Adrián Larumbe
2025-09-17 10:17 ` Steven Price
2025-09-12 13:19 ` [PATCH v3 4/4] drm/panfrost: Display list of device JM contexts over debugfs Adrián Larumbe
2025-09-17 10:17 ` Steven Price
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=20250912132002.304187-1-adrian.larumbe@collabora.com \
--to=adrian.larumbe@collabora.com \
--cc=boris.brezillon@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=steven.price@arm.com \
/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®