[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <174100406813.47174.5029499450421532895.b4-ty@imgtec.com>
Date: Mon, 3 Mar 2025 12:14:28 +0000
From: Matt Coster <matt.coster@...tec.com>
To: Frank Binns <frank.binns@...tec.com>,
Maarten Lankhorst
<maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...il.com>, Simona Vetter <simona@...ll.ch>,
Brendan King <Brendan.King@...tec.com>
CC: <dri-devel@...ts.freedesktop.org>, <linux-kernel@...r.kernel.org>,
<stable@...r.kernel.org>, Brendan King <brendan.king@...tec.com>
Subject: Re: [PATCH v2] drm/imagination: Hold drm_gem_gpuva lock for unmap
On Wed, 26 Feb 2025 15:43:06 +0000, Brendan King wrote:
> Avoid a warning from drm_gem_gpuva_assert_lock_held in drm_gpuva_unlink.
>
> The Imagination driver uses the GEM object reservation lock to protect
> the gpuva list, but the GEM object was not always known in the code
> paths that ended up calling drm_gpuva_unlink. When the GEM object isn't
> known, it is found by calling drm_gpuva_find to lookup the object
> associated with a given virtual address range, or by calling
> drm_gpuva_find_first when removing all mappings.
>
> [...]
Applied, thanks!
[1/1] drm/imagination: Hold drm_gem_gpuva lock for unmap
commit: a5c4c3ba95a52d66315acdfbaba9bd82ed39c250
Best regards,
--
Matt Coster <matt.coster@...tec.com>
Powered by blists - more mailing lists