mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Larumbe <adrian.larumbe@collabora.com>
To: Boris Brezillon <boris.brezillon@collabora.com>
Cc: Steven Price <steven.price@arm.com>,
	Liviu Dudau <liviu.dudau@arm.com>,
	 Chris Diamand <chris.diamand@arm.com>,
	Akash Goel <akash.goel@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>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 16/18] drm/panthor: Track user owned groups
Date: Fri, 11 Sep 2026 20:17:27 +0100	[thread overview]
Message-ID: <aqQLUfxvROh3soX_@sobremesa> (raw)
In-Reply-To: <20260826-panthor-unplug-fixes-v4-16-982cc8f4234b@collabora.com>

Reviewed-by: Adrián Larumbe <adrian.larumbe@collabora.com>

On 26.08.2026 16:56, Boris Brezillon wrote:
> A group can outlive its user handle because of internal refs. In order
> to fix the unplug logic, we need to keep track of groups that have a
> valid user handle so we can release the references that were owned by
> the user processes in the unplug path.
> 
> This is the prep work to keep track of user owned groups. Note that
> the destroyed attribute is dropped because it's equivalent to checking
> whether the group is inserted in the user_owned list now.
> 
> Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com>
> ---
>  drivers/gpu/drm/panthor/panthor_sched.c | 43 ++++++++++++++++++++++++---------
>  1 file changed, 31 insertions(+), 12 deletions(-)
> 
> diff --git a/drivers/gpu/drm/panthor/panthor_sched.c b/drivers/gpu/drm/panthor/panthor_sched.c
> index 4ea16b40d6b9..bd5dcf4cb580 100644
> --- a/drivers/gpu/drm/panthor/panthor_sched.c
> +++ b/drivers/gpu/drm/panthor/panthor_sched.c
> @@ -235,6 +235,15 @@ struct panthor_scheduler {
>  		 * This list is evaluated in the @sync_upd_work work.
>  		 */
>  		struct list_head waiting;
> +
> +		/**
> +		 * @user_owned: List of groups that have a valid user handle.
> +		 *
> +		 * All groups are inserted in this list at creation time through their
> +		 * panthor_group;:user_node, and evicted from this list when

                  Nit: :: instead of ;:

> +		 * panthor_group_destroy() is called.
> +		 */
> +		struct list_head user_owned;
>  	} groups;
>  
>  	/**
> @@ -586,15 +595,6 @@ struct panthor_group {
>  	 */
>  	int csg_id;
>  
> -	/**
> -	 * @destroyed: True when the group has been destroyed.
> -	 *
> -	 * If a group is destroyed it becomes useless: no further jobs can be submitted
> -	 * to its queues. We simply wait for all references to be dropped so we can
> -	 * release the group object.
> -	 */
> -	bool destroyed;
> -
>  	/**
>  	 * @timedout: True when a timeout occurred on any of the queues owned by
>  	 * this group.
> @@ -707,6 +707,17 @@ struct panthor_group {
>  	 * panthor_group::groups::waiting list.
>  	 */
>  	struct list_head wait_node;
> +
> +	/**
> +	 * @user_node: Used to insert the group in the panthor_scheduler::groups::user_owned list.
> +	 *
> +	 * When the group is created, it's inserted in panthor_scheduler::groups::user_owned,
> +	 * and when panthor_group_destroy, the group is remove from this list.
> +	 *
> +	 * When the device is unplugged, all groups that remain in this list must have an extra
> +	 * put_group() called on them to release the reference owned by the per-file group pool.
> +	 */
> +	struct list_head user_node;
>  };
>  
>  struct panthor_job_profiling_data {
> @@ -969,6 +980,7 @@ static void group_release(struct kref *kref)
>  	struct panthor_device *ptdev = group->ptdev;
>  
>  	drm_WARN_ON(&ptdev->base, group->csg_id >= 0);
> +	drm_WARN_ON(&ptdev->base, !list_empty(&group->user_node));
>  	drm_WARN_ON(&ptdev->base, !list_empty(&group->run_node));
>  	drm_WARN_ON(&ptdev->base, !list_empty(&group->wait_node));
>  
> @@ -1003,7 +1015,7 @@ group_can_run(struct panthor_group *group)
>  {
>  	return group->state != PANTHOR_CS_GROUP_TERMINATED &&
>  	       group->state != PANTHOR_CS_GROUP_UNKNOWN_STATE &&
> -	       !group->destroyed &&
> +	       !list_empty(&group->user_node) &&
>  	       !atomic_read(&group->fatal_queues) &&
>  	       !atomic_read(&group->timedout);
>  }
> @@ -2472,7 +2484,7 @@ tick_ctx_apply(struct panthor_scheduler *sched, struct panthor_sched_tick_ctx *c
>  			 * re-evaluate as soon as possible and get rid of
>  			 * this dangling group.
>  			 */
> -			if (group->destroyed)
> +			if (list_empty(&group->user_node))
>  				ctx->immediate_tick = true;
>  			group_put(group);
>  		}
> @@ -3667,6 +3679,7 @@ int panthor_group_create(struct panthor_file *pfile,
>  	group->tiler_core_mask = group_args->tiler_core_mask;
>  	group->priority = group_args->priority;
>  
> +	INIT_LIST_HEAD(&group->user_node);
>  	INIT_LIST_HEAD(&group->wait_node);
>  	INIT_LIST_HEAD(&group->run_node);
>  	INIT_WORK(&group->term_work, group_term_work);
> @@ -3735,8 +3748,13 @@ int panthor_group_create(struct panthor_file *pfile,
>  	mutex_lock(&sched->reset.lock);
>  	if (atomic_read(&sched->reset.in_progress)) {
>  		panthor_group_stop(group);
> +
> +		mutex_lock(&sched->lock);
> +		list_add_tail(&group->user_node, &sched->groups.user_owned);
> +		mutex_unlock(&sched->lock);
>  	} else {
>  		mutex_lock(&sched->lock);
> +		list_add_tail(&group->user_node, &sched->groups.user_owned);
>  		list_add_tail(&group->run_node,
>  			      &sched->groups.idle[group->priority]);
>  		mutex_unlock(&sched->lock);
> @@ -3776,7 +3794,7 @@ int panthor_group_destroy(struct panthor_file *pfile, u32 group_handle)
>  
>  	mutex_lock(&sched->reset.lock);
>  	mutex_lock(&sched->lock);
> -	group->destroyed = true;
> +	list_del_init(&group->user_node);
>  	if (group->csg_id >= 0) {
>  		sched_queue_delayed_work(sched, tick, 0);
>  	} else if (!atomic_read(&sched->reset.in_progress)) {
> @@ -4143,6 +4161,7 @@ int panthor_sched_init(struct panthor_device *ptdev)
>  		INIT_LIST_HEAD(&sched->groups.idle[prio]);
>  	}
>  	INIT_LIST_HEAD(&sched->groups.waiting);
> +	INIT_LIST_HEAD(&sched->groups.user_owned);
>  
>  	ret = drmm_mutex_init(&ptdev->base, &sched->reset.lock);
>  	if (ret)
> 
> -- 
> 2.55.0


Adrian Larumbe

  reply	other threads:[~2026-09-11 19:17 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26 14:55 [PATCH v4 00/18] drm/panthor: Fix the unplug logic Boris Brezillon
2026-08-26 14:56 ` [PATCH v4 01/18] drm/panthor: Disable reset work before unplug Boris Brezillon
2026-08-27 13:00   ` Liviu Dudau
2026-09-10  1:12   ` Adrian Larumbe
2026-08-26 14:56 ` [PATCH v4 02/18] drm/panthor: Revisit the reset logic to avoid reset request loss Boris Brezillon
2026-08-27 15:04   ` Liviu Dudau
2026-09-10  1:13   ` Adrian Larumbe
2026-08-26 14:56 ` [PATCH v4 03/18] drm/panthor: Make panthor_device::pm::state non-atomic Boris Brezillon
2026-08-27 15:12   ` Liviu Dudau
2026-09-10  1:13   ` Adrian Larumbe
2026-08-26 14:56 ` [PATCH v4 04/18] drm/panthor: Flush the cleanup_wq in the unplug path Boris Brezillon
2026-08-27 15:14   ` Liviu Dudau
2026-09-10  1:14   ` Adrian Larumbe
2026-08-26 14:56 ` [PATCH v4 05/18] drm/panthor: Make the page table cache and cleanup workqueue device-local Boris Brezillon
2026-08-27 15:20   ` Liviu Dudau
2026-09-10  1:14   ` Adrian Larumbe
2026-08-26 14:56 ` [PATCH v4 06/18] drm/panthor: Drop unused vm argument passed to panthor_vm_prepare_sync_only_op_ctx() Boris Brezillon
2026-08-27 15:21   ` Liviu Dudau
2026-09-10  1:15   ` Adrian Larumbe
2026-08-26 14:56 ` [PATCH v4 07/18] drm/panthor: Move the debugfs initialization to panthor_device.c Boris Brezillon
2026-09-10  1:18   ` Adrian Larumbe
2026-08-26 14:56 ` [PATCH v4 08/18] drm/panthor: Split panthor_vm Boris Brezillon
2026-09-11  3:37   ` Adrian Larumbe
2026-09-11  9:48     ` Boris Brezillon
2026-08-26 14:56 ` [PATCH v4 09/18] drm/panthor: Add fine-grained restrictions on VMs Boris Brezillon
2026-09-11  3:38   ` Adrian Larumbe
2026-08-26 14:56 ` [PATCH v4 10/18] drm/panthor: Check AS state before disabling Boris Brezillon
2026-09-11  3:38   ` Adrian Larumbe
2026-08-26 14:56 ` [PATCH v4 11/18] drm/panthor: Don't pre-allocate VMAs or page tables when preparing a full VM unmap Boris Brezillon
2026-09-11  3:38   ` Adrian Larumbe
2026-08-26 14:56 ` [PATCH v4 12/18] drm/panthor: Let l2_power_off return errors and force users to check it Boris Brezillon
2026-09-11  3:39   ` Adrian Larumbe
2026-08-26 14:56 ` [PATCH v4 13/18] drm/panthor: Complain if the SOFT_RESET fails Boris Brezillon
2026-09-11  3:40   ` Adrian Larumbe
2026-09-11  9:54     ` Boris Brezillon
2026-08-26 14:56 ` [PATCH v4 14/18] drm/panthor: Make the VM cleanup path more robust against UAF Boris Brezillon
2026-09-11 19:15   ` Adrian Larumbe
2026-08-26 14:56 ` [PATCH v4 15/18] drm/panthor: Track user owned VMs Boris Brezillon
2026-09-11 19:17   ` Adrian Larumbe
2026-08-26 14:56 ` [PATCH v4 16/18] drm/panthor: Track user owned groups Boris Brezillon
2026-09-11 19:17   ` Adrian Larumbe [this message]
2026-08-26 14:56 ` [PATCH v4 17/18] drm/panthor: Fix the unplug logic Boris Brezillon
2026-08-26 14:56 ` [PATCH v4 18/18] drm/panthor: Add debugfs knobs to simulate reset failures Boris Brezillon
2026-09-11 19:18   ` Adrian Larumbe

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=aqQLUfxvROh3soX_@sobremesa \
    --to=adrian.larumbe@collabora.com \
    --cc=airlied@gmail.com \
    --cc=akash.goel@arm.com \
    --cc=boris.brezillon@collabora.com \
    --cc=chris.diamand@arm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --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

all inboxes | Powered by JetHome®