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>,
nd@arm.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 4/5] drm/panthor: Propagate VM-level faults to groups
Date: Mon, 15 Dec 2025 13:41:24 +0100 [thread overview]
Message-ID: <20251215134124.6ddca7f0@fedora> (raw)
In-Reply-To: <20251215115457.2137485-5-lukas.zapolskas@arm.com>
On Mon, 15 Dec 2025 11:54:56 +0000
Lukas Zapolskas <lukas.zapolskas@arm.com> wrote:
> Receiving an MMU fault currently disables the AS, so each of the groups
> is marked with the appropriate faults. Since no further submissions
> can occur on a fatal fault for that group, the fault information
> does not have to be cleared until the group is terminated.
>
> Signed-off-by: Lukas Zapolskas <lukas.zapolskas@arm.com>
> ---
> drivers/gpu/drm/panthor/panthor_mmu.c | 8 ++++++++
> drivers/gpu/drm/panthor/panthor_mmu.h | 2 ++
> drivers/gpu/drm/panthor/panthor_sched.c | 13 +++++++++++++
> 3 files changed, 23 insertions(+)
>
> diff --git a/drivers/gpu/drm/panthor/panthor_mmu.c b/drivers/gpu/drm/panthor/panthor_mmu.c
> index 10a7418eecda..9e78b0509f1a 100644
> --- a/drivers/gpu/drm/panthor/panthor_mmu.c
> +++ b/drivers/gpu/drm/panthor/panthor_mmu.c
> @@ -2895,3 +2895,11 @@ void panthor_mmu_pt_cache_fini(void)
> {
> kmem_cache_destroy(pt_cache);
> }
> +
> +struct panthor_vm_fault *panthor_vm_get_fault(struct panthor_vm *vm)
const struct panthor_vm_fault *
panthor_vm_get_fault(struct panthor_vm *vm)
or
struct panthor_vm_fault
panthor_vm_get_fault(struct panthor_vm *vm)
or
void
panthor_vm_get_fault(struct panthor_vm *vm,
struct panthor_vm_fault *fault)
but you shouldn't let the caller with a writable pointer to vm->fault.
> +{
> + if (!vm)
> + return NULL;
I don't see a valid case where panthor_vm_get_fault() would be called
with a NULL pointer.
> +
> + return &vm->fault;
> +}
> diff --git a/drivers/gpu/drm/panthor/panthor_mmu.h b/drivers/gpu/drm/panthor/panthor_mmu.h
> index 023fdc79c231..d69b4000a39e 100644
> --- a/drivers/gpu/drm/panthor/panthor_mmu.h
> +++ b/drivers/gpu/drm/panthor/panthor_mmu.h
> @@ -123,4 +123,6 @@ void panthor_mmu_pt_cache_fini(void);
> void panthor_mmu_debugfs_init(struct drm_minor *minor);
> #endif
>
> +struct panthor_vm_fault *panthor_vm_get_fault(struct panthor_vm *vm);
> +
> #endif
> diff --git a/drivers/gpu/drm/panthor/panthor_sched.c b/drivers/gpu/drm/panthor/panthor_sched.c
> index a77399e95620..9ea0d2b27114 100644
> --- a/drivers/gpu/drm/panthor/panthor_sched.c
> +++ b/drivers/gpu/drm/panthor/panthor_sched.c
> @@ -722,6 +722,11 @@ struct panthor_group {
> * panthor_group::groups::waiting list.
> */
> struct list_head wait_node;
> +
> + /**
> + * @fatal: VM-level fault that caused a fatal error on the group.
> + */
> + struct panthor_vm_fault fatal;
> };
>
> struct panthor_job_profiling_data {
> @@ -1575,6 +1580,14 @@ cs_slot_process_fatal_event_locked(struct panthor_device *ptdev,
> group->task_info.pid, group->task_info.comm);
>
> group->fatal_queues |= BIT(cs_id);
> +
> + if (panthor_vm_has_unhandled_faults(group->vm)) {
> + struct panthor_vm_fault *fault;
> +
> + fault = panthor_vm_get_fault(group->vm);
> + if (fault)
> + group->fatal = *fault;
> + }
> }
>
> if (CS_EXCEPTION_TYPE(fatal) == DRM_PANTHOR_EXCEPTION_CS_UNRECOVERABLE) {
next prev parent reply other threads:[~2025-12-15 12:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 11:54 [PATCH v1 0/5] drm/panthor: Implement fault information propagation Lukas Zapolskas
2025-12-15 11:54 ` [PATCH v1 1/5] drm/panthor: Implement CS_FAULT propagation to userspace Lukas Zapolskas
2025-12-15 12:03 ` Boris Brezillon
2025-12-15 11:54 ` [PATCH v1 2/5] drm/panthor: Store queue fault and fatal information Lukas Zapolskas
2025-12-15 12:11 ` Boris Brezillon
2025-12-17 11:37 ` Steven Price
2025-12-15 11:54 ` [PATCH v1 3/5] drm/panthor: Track VM faults Lukas Zapolskas
2025-12-15 12:37 ` Boris Brezillon
2025-12-15 11:54 ` [PATCH v1 4/5] drm/panthor: Propagate VM-level faults to groups Lukas Zapolskas
2025-12-15 12:41 ` Boris Brezillon [this message]
2025-12-15 12:46 ` Boris Brezillon
2025-12-15 11:54 ` [PATCH v1 5/5] drm/panthor: Use GROUP_GET_STATE to provide group and queue errors Lukas Zapolskas
2025-12-15 17:31 ` Boris Brezillon
2025-12-16 5:45 ` kernel test robot
2025-12-16 7:52 ` Marcin Ślusarz
2025-12-16 9:29 ` kernel test robot
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=20251215134124.6ddca7f0@fedora \
--to=boris.brezillon@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=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;
as well as URLs for NNTP newsgroup(s).