From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by smtp.subspace.kernel.org (Postfix) with ESMTP id A3D832BDC16 for ; Fri, 19 Dec 2025 10:42:10 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=217.140.110.172 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766140932; cv=none; b=S0yvpriL9Li3fROl+CbNqarze/fVKHD1BvmdNdUr7S3KII4IQc9S/aOM4SD2AWFjxWS23eTrUPTddymd94j5Qt7NuR/OCWCI+r7vfkZZwO6WASlRTVQ7nOkDZ7rC4891tJYZuktV7sSdzv8mXFLE0N8n129KFIIW7rlVGpbaW/0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766140932; c=relaxed/simple; bh=lSZE8IiknvVPYgeiVWy66NdEBWujtZjIHdFUGkLkZLc=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=ul315aKR78iNuLlZWNhSsj3X1YoQzZdCdU0h/rgmpjg+4cPDmRX0L7pWbAzqOMN6qSEWtoTT0UuYaiaRIBFqdL7xOGs7G/f2R0XNY03j5rgh5TuA24FHPoPT467Cn5QOcnrKPApaLVph9TAcfTS/N1HZriUDekefCr7Bm2wXPhU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com; spf=pass smtp.mailfrom=arm.com; arc=none smtp.client-ip=217.140.110.172 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=arm.com Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id C5473106F for ; Fri, 19 Dec 2025 02:42:02 -0800 (PST) Received: from [192.168.0.1] (usa-sjc-imap-foss1.foss.arm.com [10.121.207.14]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id A831B3F5CA for ; Fri, 19 Dec 2025 02:42:09 -0800 (PST) Date: Fri, 19 Dec 2025 10:41:13 +0000 From: Liviu Dudau To: Ketil Johnsen Cc: Boris Brezillon , Steven Price , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Simona Vetter , Grant Likely , Heiko Stuebner , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] drm/panthor: Evict groups before VM termination Message-ID: References: <20251219093546.1227697-1-ketil.johnsen@arm.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20251219093546.1227697-1-ketil.johnsen@arm.com> On Fri, Dec 19, 2025 at 10:35:44AM +0100, Ketil Johnsen wrote: > Ensure all related groups are evicted and suspended before VM > destruction takes place. > > This fixes an issue where panthor_vm_destroy() destroys and unmaps the > heap context while there are still on slot groups using this. > The FW will do a write out to the heap context when a CSG (group) is > suspended, so a premature unmap of the heap context will cause a > GPU page fault. > This page fault is quite harmless, and do not affect the continued > operation of the GPU. > > Fixes: 647810ec2476 ("drm/panthor: Add the MMU/VM logical block") > Reviewed-by: Boris Brezillon > Co-developed-by: Boris Brezillon > Signed-off-by: Ketil Johnsen Reviewed-by: Liviu Dudau Best regards, Liviu > --- > Changes in v2: > - Removed check for ptdev->scheduler > - R-b from Boris > - Link to v1: https://lore.kernel.org/all/20251218162644.828495-1-ketil.johnsen@arm.com/ > --- > drivers/gpu/drm/panthor/panthor_mmu.c | 4 ++++ > drivers/gpu/drm/panthor/panthor_sched.c | 14 ++++++++++++++ > drivers/gpu/drm/panthor/panthor_sched.h | 1 + > 3 files changed, 19 insertions(+) > > diff --git a/drivers/gpu/drm/panthor/panthor_mmu.c b/drivers/gpu/drm/panthor/panthor_mmu.c > index 74230f7199121..0e4b301a9c70e 100644 > --- a/drivers/gpu/drm/panthor/panthor_mmu.c > +++ b/drivers/gpu/drm/panthor/panthor_mmu.c > @@ -1537,6 +1537,10 @@ static void panthor_vm_destroy(struct panthor_vm *vm) > > vm->destroyed = true; > > + /* Tell scheduler to stop all GPU work related to this VM */ > + if (refcount_read(&vm->as.active_cnt) > 0) > + panthor_sched_prepare_for_vm_destruction(vm->ptdev); > + > mutex_lock(&vm->heaps.lock); > panthor_heap_pool_destroy(vm->heaps.pool); > vm->heaps.pool = NULL; > diff --git a/drivers/gpu/drm/panthor/panthor_sched.c b/drivers/gpu/drm/panthor/panthor_sched.c > index f680edcd40aad..a40ac94e5e989 100644 > --- a/drivers/gpu/drm/panthor/panthor_sched.c > +++ b/drivers/gpu/drm/panthor/panthor_sched.c > @@ -2930,6 +2930,20 @@ void panthor_sched_report_mmu_fault(struct panthor_device *ptdev) > sched_queue_delayed_work(ptdev->scheduler, tick, 0); > } > > +void panthor_sched_prepare_for_vm_destruction(struct panthor_device *ptdev) > +{ > + /* FW can write out internal state, like the heap context, during CSG > + * suspend. It is therefore important that the scheduler has fully > + * evicted any pending and related groups before VM destruction can > + * safely continue. Failure to do so can lead to GPU page faults. > + * A controlled termination of a Panthor instance involves destroying > + * the group(s) before the VM. This means any relevant group eviction > + * has already been initiated by this point, and we just need to > + * ensure that any pending tick_work() has been completed. > + */ > + flush_work(&ptdev->scheduler->tick_work.work); > +} > + > void panthor_sched_resume(struct panthor_device *ptdev) > { > /* Force a tick to re-evaluate after a resume. */ > diff --git a/drivers/gpu/drm/panthor/panthor_sched.h b/drivers/gpu/drm/panthor/panthor_sched.h > index f4a475aa34c0a..9a8692de8aded 100644 > --- a/drivers/gpu/drm/panthor/panthor_sched.h > +++ b/drivers/gpu/drm/panthor/panthor_sched.h > @@ -50,6 +50,7 @@ void panthor_sched_suspend(struct panthor_device *ptdev); > void panthor_sched_resume(struct panthor_device *ptdev); > > void panthor_sched_report_mmu_fault(struct panthor_device *ptdev); > +void panthor_sched_prepare_for_vm_destruction(struct panthor_device *ptdev); > void panthor_sched_report_fw_events(struct panthor_device *ptdev, u32 events); > > void panthor_fdinfo_gather_group_samples(struct panthor_file *pfile); > -- > 2.43.0 >