<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/gpu/drm/lima/lima_gem.c, branch linux-rolling-stable</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-rolling-stable</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-rolling-stable'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2025-05-28T14:15:58Z</updated>
<entry>
<title>drm/sched: Store the drm client_id in drm_sched_fence</title>
<updated>2025-05-28T14:15:58Z</updated>
<author>
<name>Pierre-Eric Pelloux-Prayer</name>
</author>
<published>2025-05-26T12:54:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2956554823cedb390b7ec4534afa898176317638'/>
<id>urn:sha1:2956554823cedb390b7ec4534afa898176317638</id>
<content type='text'>
This will be used in a later commit to trace the drm client_id in
some of the gpu_scheduler trace events.

This requires changing all the users of drm_sched_job_init to
add an extra parameter.

The newly added drm_client_id field in the drm_sched_fence is a bit
of a duplicate of the owner one. One suggestion I received was to
merge those 2 fields - this can't be done right now as amdgpu uses
some special values (AMDGPU_FENCE_OWNER_*) that can't really be
translated into a client id. Christian is working on getting rid of
those; when it's done we should be able to squash owner/drm_client_id
together.

Reviewed-by: Christian König &lt;christian.koenig@amd.com&gt;
Signed-off-by: Pierre-Eric Pelloux-Prayer &lt;pierre-eric.pelloux-prayer@amd.com&gt;
Signed-off-by: Philipp Stanner &lt;phasta@kernel.org&gt;
Link: https://lore.kernel.org/r/20250526125505.2360-3-pierre-eric.pelloux-prayer@amd.com
</content>
</entry>
<entry>
<title>drm/shmem-helper: Use refcount_t for pages_use_count</title>
<updated>2025-03-26T20:00:19Z</updated>
<author>
<name>Dmitry Osipenko</name>
</author>
<published>2025-03-22T21:26:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=051b6646d36dc974c3884d75021bf282925b171c'/>
<id>urn:sha1:051b6646d36dc974c3884d75021bf282925b171c</id>
<content type='text'>
Use atomic refcount_t helper for pages_use_count to optimize pin/unpin
functions by skipping reservation locking while GEM's pin refcount &gt; 1.

Acked-by: Maxime Ripard &lt;mripard@kernel.org&gt;
Reviewed-by: Boris Brezillon &lt;boris.brezillon@collabora.com&gt;
Suggested-by: Boris Brezillon &lt;boris.brezillon@collabora.com&gt;
Acked-by: Thomas Zimmermann &lt;tzimmermann@suse.d&gt;
Signed-off-by: Dmitry Osipenko &lt;dmitry.osipenko@collabora.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20250322212608.40511-9-dmitry.osipenko@collabora.com
</content>
</entry>
<entry>
<title>drm/shmem-helper: Refactor locked/unlocked functions</title>
<updated>2025-03-26T20:00:12Z</updated>
<author>
<name>Dmitry Osipenko</name>
</author>
<published>2025-03-22T21:26:03Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=954907f7147dc43e0d1cd4d430c21d143d5fdf55'/>
<id>urn:sha1:954907f7147dc43e0d1cd4d430c21d143d5fdf55</id>
<content type='text'>
Add locked and remove unlocked postfixes from drm-shmem function names,
making names consistent with the drm/gem core code.

Reviewed-by: Boris Brezillon &lt;boris.brezillon@collabora.com&gt;
Suggested-by: Boris Brezillon &lt;boris.brezillon@collabora.com&gt;
Acked-by: Thomas Zimmermann &lt;tzimmermann@suse.d&gt;
Signed-off-by: Dmitry Osipenko &lt;dmitry.osipenko@collabora.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20250322212608.40511-6-dmitry.osipenko@collabora.com
</content>
</entry>
<entry>
<title>drm/lima: Fix dma_resv deadlock at drm object pin time</title>
<updated>2024-05-29T07:30:39Z</updated>
<author>
<name>Adrián Larumbe</name>
</author>
<published>2024-05-23T11:32:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8c2f5dd0c362ec036f0217da1d413ce2b8361080'/>
<id>urn:sha1:8c2f5dd0c362ec036f0217da1d413ce2b8361080</id>
<content type='text'>
Commit a78027847226 ("drm/gem: Acquire reservation lock in
drm_gem_{pin/unpin}()") moved locking the DRM object's dma reservation to
drm_gem_pin(), but Lima's pin callback kept calling drm_gem_shmem_pin,
which also tries to lock the same dma_resv, leading to a double lock
situation.

As was already done for Panfrost in the previous commit, fix it by
replacing drm_gem_shmem_pin() with its locked variant.

Cc: Thomas Zimmermann &lt;tzimmermann@suse.de&gt;
Cc: Dmitry Osipenko &lt;dmitry.osipenko@collabora.com&gt;
Cc: Boris Brezillon &lt;boris.brezillon@collabora.com&gt;
Cc: Steven Price &lt;steven.price@arm.com&gt;
Fixes: a78027847226 ("drm/gem: Acquire reservation lock in drm_gem_{pin/unpin}()")
Signed-off-by: Adrián Larumbe &lt;adrian.larumbe@collabora.com&gt;
Reviewed-by: Boris Brezillon &lt;boris.brezillon@collabora.com&gt;
Tested-by: Val Packett &lt;val@packett.cool&gt;
Signed-off-by: Boris Brezillon &lt;boris.brezillon@collabora.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20240523113236.432585-3-adrian.larumbe@collabora.com
</content>
</entry>
<entry>
<title>drm/lima: fix a memleak in lima_heap_alloc</title>
<updated>2024-01-19T02:12:01Z</updated>
<author>
<name>Zhipeng Lu</name>
</author>
<published>2024-01-17T07:13:28Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=04ae3eb470e52a3c41babe85ff8cee195e4dcbea'/>
<id>urn:sha1:04ae3eb470e52a3c41babe85ff8cee195e4dcbea</id>
<content type='text'>
When lima_vm_map_bo fails, the resources need to be deallocated, or
there will be memleaks.

Fixes: 6aebc51d7aef ("drm/lima: support heap buffer creation")
Signed-off-by: Zhipeng Lu &lt;alexious@zju.edu.cn&gt;
Signed-off-by: Qiang Yu &lt;yuq825@gmail.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20240117071328.3811480-1-alexious@zju.edu.cn
</content>
</entry>
<entry>
<title>drm/shmem-helper: Switch to reservation lock</title>
<updated>2023-06-21T17:22:20Z</updated>
<author>
<name>Dmitry Osipenko</name>
</author>
<published>2023-05-29T22:39:35Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=21aa27ddc58269349597c6d243212bcc4065d277'/>
<id>urn:sha1:21aa27ddc58269349597c6d243212bcc4065d277</id>
<content type='text'>
Replace all drm-shmem locks with a GEM reservation lock. This makes locks
consistent with dma-buf locking convention where importers are responsible
for holding reservation lock for all operations performed over dma-bufs,
preventing deadlock between dma-buf importers and exporters.

Suggested-by: Daniel Vetter &lt;daniel@ffwll.ch&gt;
Acked-by: Thomas Zimmermann &lt;tzimmermann@suse.de&gt;
Reviewed-by: Emil Velikov &lt;emil.l.velikov@gmail.com&gt;
Signed-off-by: Dmitry Osipenko &lt;dmitry.osipenko@collabora.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20230529223935.2672495-7-dmitry.osipenko@collabora.com
</content>
</entry>
<entry>
<title>drm/lima: Use drm_sched_job_add_syncobj_dependency()</title>
<updated>2023-03-21T21:14:19Z</updated>
<author>
<name>Maíra Canal</name>
</author>
<published>2023-02-24T21:41:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e0dfefa08d94bf548fbbbbae22e4720a652a3102'/>
<id>urn:sha1:e0dfefa08d94bf548fbbbbae22e4720a652a3102</id>
<content type='text'>
As lima_gem_add_deps() performs the same steps as
drm_sched_job_add_syncobj_dependency(), replace the open-coded
implementation in Lima in order to simply use the DRM function.

Signed-off-by: Maíra Canal &lt;mcanal@igalia.com&gt;
Reviewed-by: Qiang Yu &lt;yuq825@gmail.com&gt;
Signed-off-by: Maíra Canal &lt;mairacanal@riseup.net&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20230224214133.411966-1-mcanal@igalia.com
</content>
</entry>
<entry>
<title>Revert "drm/shmem-helper: Switch to reservation lock"</title>
<updated>2023-02-28T15:41:32Z</updated>
<author>
<name>Thomas Zimmermann</name>
</author>
<published>2023-02-28T15:26:12Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e0106ac97886b6bc36c480de72562d3e70b3f8b1'/>
<id>urn:sha1:e0106ac97886b6bc36c480de72562d3e70b3f8b1</id>
<content type='text'>
This reverts commit 67b7836d4458790f1261e31fe0ce3250989784f0.

The locking appears incomplete. A caller of SHMEM helper's pin
function never acquires the dma-buf reservation lock. So we get

  WARNING: CPU: 3 PID: 967 at drivers/gpu/drm/drm_gem_shmem_helper.c:243 drm_gem_shmem_pin+0x42/0x90 [drm_shmem_helper]

Signed-off-by: Thomas Zimmermann &lt;tzimmermann@suse.de&gt;
Acked-by: Dmitry Osipenko &lt;dmitry.osipenko@collabora.com&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20230228152612.19971-1-tzimmermann@suse.de
</content>
</entry>
<entry>
<title>drm/shmem-helper: Switch to reservation lock</title>
<updated>2023-02-27T04:10:56Z</updated>
<author>
<name>Dmitry Osipenko</name>
</author>
<published>2022-03-21T00:35:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=67b7836d4458790f1261e31fe0ce3250989784f0'/>
<id>urn:sha1:67b7836d4458790f1261e31fe0ce3250989784f0</id>
<content type='text'>
Replace all drm-shmem locks with a GEM reservation lock. This makes locks
consistent with dma-buf locking convention where importers are responsible
for holding reservation lock for all operations performed over dma-bufs,
preventing deadlock between dma-buf importers and exporters.

Suggested-by: Daniel Vetter &lt;daniel@ffwll.ch&gt;
Acked-by: Thomas Zimmermann &lt;tzimmermann@suse.de&gt;
Signed-off-by: Dmitry Osipenko &lt;dmitry.osipenko@collabora.com&gt;
Link: https://lore.kernel.org/all/20230108210445.3948344-8-dmitry.osipenko@collabora.com/
</content>
</entry>
<entry>
<title>dma-buf: specify usage while adding fences to dma_resv obj v7</title>
<updated>2022-04-07T10:53:53Z</updated>
<author>
<name>Christian König</name>
</author>
<published>2021-11-09T10:08:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=73511edf8b196e6f1ccda0fdf294ff57aa2dc9db'/>
<id>urn:sha1:73511edf8b196e6f1ccda0fdf294ff57aa2dc9db</id>
<content type='text'>
Instead of distingting between shared and exclusive fences specify
the fence usage while adding fences.

Rework all drivers to use this interface instead and deprecate the old one.

v2: some kerneldoc comments suggested by Daniel
v3: fix a missing case in radeon
v4: rebase on nouveau changes, fix lockdep and temporary disable warning
v5: more documentation updates
v6: separate internal dma_resv changes from this patch, avoids to
    disable warning temporary, rebase on upstream changes
v7: fix missed case in lima driver, minimize changes to i915_gem_busy_ioctl

Signed-off-by: Christian König &lt;christian.koenig@amd.com&gt;
Reviewed-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Link: https://patchwork.freedesktop.org/patch/msgid/20220407085946.744568-3-christian.koenig@amd.com
</content>
</entry>
</feed>
