From: Steven Price <steven.price@arm.com>
To: "Adrián Larumbe" <adrian.larumbe@collabora.com>,
linux-kernel@vger.kernel.org
Cc: dri-devel@lists.freedesktop.org,
Boris Brezillon <boris.brezillon@collabora.com>,
kernel@collabora.com
Subject: Re: [PATCH v4 0/4] Introduce Panfrost JM contexts
Date: Thu, 18 Sep 2025 14:58:46 +0100 [thread overview]
Message-ID: <8434d14e-827d-4652-b4f8-06e2aa4caa41@arm.com> (raw)
In-Reply-To: <20250917191859.500279-1-adrian.larumbe@collabora.com>
On 17/09/2025 20:18, Adrián Larumbe wrote:
> 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/
>
> Discussion of the previous patch series revision can be found at:
> https://lore.kernel.org/dri-devel/20250912132002.304187-1-adrian.larumbe@collabora.com/
Pushed to drm-misc-next.
Thanks,
Steve
>
> Changelog:
> v4:
> - Iterate over all the indices for the scheduler entity array when creating,
> releasing or otherwise destroying a job context, in case someone would want to
> implement compute support in the future.
> - Add R-b tags to other patches.
> 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
prev parent reply other threads:[~2025-09-18 13:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 19:18 Adrián Larumbe
2025-09-17 19:18 ` [PATCH v4 1/4] drm/panfrost: Introduce uAPI for JM context creation Adrián Larumbe
2025-09-17 19:18 ` [PATCH v4 2/4] drm/panfrost: Introduce JM contexts for manging job resources Adrián Larumbe
2025-09-18 12:47 ` Steven Price
2025-09-17 19:18 ` [PATCH v4 3/4] drm/panfrost: Expose JM context IOCTLs to UM Adrián Larumbe
2025-09-17 19:18 ` [PATCH v4 4/4] drm/panfrost: Display list of device JM contexts over debugfs Adrián Larumbe
2025-09-18 13:58 ` Steven Price [this message]
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=8434d14e-827d-4652-b4f8-06e2aa4caa41@arm.com \
--to=steven.price@arm.com \
--cc=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 \
/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®