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 15/18] drm/panthor: Track user owned VMs
Date: Fri, 11 Sep 2026 20:17:07 +0100 [thread overview]
Message-ID: <aqQTkeakkiMdTfcE@sobremesa> (raw)
In-Reply-To: <20260826-panthor-unplug-fixes-v4-15-982cc8f4234b@collabora.com>
Reviewed-by: Adrián Larumbe <adrian.larumbe@collabora.com>
On 26.08.2026 16:56, Boris Brezillon wrote:
> We will soon need this to fix the unplug logic and make sure panthor_vm
> objects are not left behind after an unplug.
>
> Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com>
> ---
> drivers/gpu/drm/panthor/panthor_mmu.c | 31 +++++++++++++++++++++++++++----
> 1 file changed, 27 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/panthor/panthor_mmu.c b/drivers/gpu/drm/panthor/panthor_mmu.c
> index 47c57b39bd12..6368bf57b8f5 100644
> --- a/drivers/gpu/drm/panthor/panthor_mmu.c
> +++ b/drivers/gpu/drm/panthor/panthor_mmu.c
> @@ -117,12 +117,15 @@ struct panthor_mmu {
>
> /** @vm: VMs management fields */
> struct {
> - /** @vm.lock: Lock protecting access to list. */
> + /** @vm.lock: Lock protecting access to list and user_owned. */
> struct mutex lock;
>
> /** @vm.list: List containing all VMs. */
> struct list_head list;
>
> + /** @vm.list: List containing VMs with a valid handle. */
> + struct list_head user_owned;
> +
> /** @vm.reset_in_progress: True if a reset is in progress. */
> bool reset_in_progress;
>
> @@ -447,6 +450,9 @@ struct panthor_vm {
> /** @node: Used to insert the VM in the panthor_mmu::vm::list. */
> struct list_head node;
>
> + /* @user_node: Used to insert the VM in the panthor_mmu::vm::user_owned list. */
> + struct list_head user_node;
> +
> /** @for_mcu: True if this is the MCU VM. */
> bool for_mcu;
>
> @@ -1681,10 +1687,19 @@ int panthor_vm_pool_create_vm(struct panthor_device *ptdev,
> drm_gem_object_get(&pool->dummy->base);
> vm->dummy = pool->dummy;
>
> + /* Insert in the list before xa_alloc() so we can't race with
> + * panthor_vm_pool_destroy_vm() have the VM inserted in the
> + * user_owned list after it's been destroyed.
> + */
> + scoped_guard(mutex, &ptdev->mmu->vm.lock)
> + list_add_tail(&vm->user_node, &ptdev->mmu->vm.user_owned);
> +
> ret = xa_alloc(&pool->xa, &id, vm,
> XA_LIMIT(1, PANTHOR_MAX_VMS_PER_FILE), GFP_KERNEL);
>
> if (ret) {
> + scoped_guard(mutex, &ptdev->mmu->vm.lock)
> + list_del_init(&vm->user_node);
> panthor_vm_put(vm);
> return ret;
> }
> @@ -1739,13 +1754,19 @@ static void panthor_vm_destroy(struct panthor_vm *vm)
> */
> int panthor_vm_pool_destroy_vm(struct panthor_vm_pool *pool, u32 handle)
> {
> + struct panthor_device *ptdev;
> struct panthor_vm *vm;
>
> vm = xa_erase(&pool->xa, handle);
> + if (!vm)
> + return -EINVAL;
> +
> + ptdev = container_of(vm->as->base.drm, struct panthor_device, base);
> + scoped_guard(mutex, &ptdev->mmu->vm.lock)
> + list_del_init(&vm->user_node);
>
> panthor_vm_destroy(vm);
> -
> - return vm ? 0 : -EINVAL;
> + return 0;
> }
>
> /**
> @@ -1785,7 +1806,7 @@ void panthor_vm_pool_destroy(struct panthor_file *pfile)
> return;
>
> xa_for_each(&pfile->vms->xa, i, vm)
> - panthor_vm_destroy(vm);
> + panthor_vm_pool_destroy_vm(pfile->vms, i);
>
> if (pfile->vms->dummy)
> drm_gem_object_put(&pfile->vms->dummy->base);
> @@ -3182,6 +3203,7 @@ panthor_vm_create(struct panthor_device *ptdev, bool for_mcu,
> goto err_put_as;
> }
>
> + INIT_LIST_HEAD(&vm->user_node);
> vm->user_va_range = kernel_va_start;
> vm->as = as;
> mutex_init(&vm->heaps.lock);
> @@ -3707,6 +3729,7 @@ int panthor_mmu_init(struct panthor_device *ptdev)
> return ret;
>
> INIT_LIST_HEAD(&mmu->vm.list);
> + INIT_LIST_HEAD(&mmu->vm.user_owned);
> ret = drmm_mutex_init(&ptdev->base, &mmu->vm.lock);
> if (ret)
> return ret;
>
> --
> 2.55.0
Adrian Larumbe
next prev parent 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 [this message]
2026-08-26 14:56 ` [PATCH v4 16/18] drm/panthor: Track user owned groups Boris Brezillon
2026-09-11 19:17 ` Adrian Larumbe
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=aqQTkeakkiMdTfcE@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®