From: "Timur Kristóf" <timur.kristof@gmail.com>
To: Philipp Stanner <phasta@kernel.org>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, amd-gfx@lists.freedesktop.org,
etnaviv@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
imagination@lists.freedesktop.org, lima@lists.freedesktop.org,
linux-arm-msm@vger.kernel.org, freedreno@lists.freedesktop.org,
nouveau@lists.freedesktop.org, virtualization@lists.linux.dev,
spice-devel@lists.freedesktop.org,
intel-xe@lists.freedesktop.org, linux-tegra@vger.kernel.org,
linux-iio@vger.kernel.org, linux-usb@vger.kernel.org,
rust-for-linux@vger.kernel.or
Subject: Re: [PATCH 0/3] dma-buf: dma-fence: Remove dma_fence_init64()
Date: Thu, 05 Nov 2026 17:32:42 +0100 [thread overview]
Message-ID: <0e3689d102abf41b1e788402cc9da354d5c2d969.camel@gmail.com> (raw)
In-Reply-To: <20261105113529.1989375-2-phasta@kernel.org>
On Thu, 2026-11-05 at 12:35 +0100, Philipp Stanner wrote:
> We recently had a discussion about reworking dma_fence init to close
> a
> race-window [1].
>
> The community agreement seems to have been that we can get rid of
> dma_fence_init64(), so let's do that already. In the meantime we can
> continue our discussions regarding the race in [1].
>
> This also touches the Rust dma_fence, which actually should use 64-
> bit
> seqnos (was forgotten so far). Rust fence has no users currently, so
> needs no backporting, so I would like to address that in a distinct
> patch.
>
> Tested on Nouveau with and without the SEQNO64 flag. Nouveau also
> uses
> the USER flag, so I hope we're fine.
>
>
> P.
>
> [1]
> https://lore.kernel.org/dri-devel/20261029095542.1526750-3-phasta@kernel.org/
Makes good sense to me.
For the entire series:
Reviewed-by: Timur Kristóf <timur.kristof@gmail.com>
(ps. I had to remove some recipients from this email because the
original had more than 100 recipients and gmail wouldn't let me reply
to all of them. Apologies for that.)
>
>
> Philipp Stanner (3):
> dma-buf: dma-fence: Add flags parameter to dma_fence_init()
> dma-buf: Port users of dma_fence_init64()
> dma-buf: dma-fence: Remove dma_fence_init64()
>
> drivers/accel/amdxdna/amdxdna_ctx.c | 2 +-
> drivers/accel/ethosu/ethosu_job.c | 2 +-
> drivers/accel/ivpu/ivpu_job.c | 2 +-
> drivers/accel/rocket/rocket_job.c | 2 +-
> drivers/dma-buf/dma-fence-array.c | 2 +-
> drivers/dma-buf/dma-fence-chain.c | 4 +-
> drivers/dma-buf/dma-fence.c | 58 +++++++++--------
> --
> drivers/dma-buf/st-dma-fence-chain.c | 2 +-
> drivers/dma-buf/st-dma-fence-unwrap.c | 2 +-
> drivers/dma-buf/st-dma-fence.c | 2 +-
> drivers/dma-buf/st-dma-resv.c | 2 +-
> drivers/dma-buf/sw_sync.c | 2 +-
> .../gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c | 2 +-
> .../drm/amd/amdgpu/amdgpu_eviction_fence.c | 7 ++-
> drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c | 2 +-
> .../gpu/drm/amd/amdgpu/amdgpu_userq_fence.c | 5 +-
> .../gpu/drm/amd/amdgpu/amdgpu_vm_tlb_fence.c | 5 +-
> drivers/gpu/drm/drm_crtc.c | 2 +-
> drivers/gpu/drm/drm_writeback.c | 2 +-
> drivers/gpu/drm/etnaviv/etnaviv_gpu.c | 2 +-
> drivers/gpu/drm/i915/gem/i915_gem_ttm_move.c | 2 +-
> drivers/gpu/drm/i915/i915_request.c | 2 +-
> drivers/gpu/drm/i915/i915_sw_fence_work.c | 2 +-
> drivers/gpu/drm/i915/i915_vma_resource.c | 2 +-
> .../gpu/drm/i915/selftests/i915_sw_fence.c | 2 +-
> drivers/gpu/drm/imagination/pvr_ccb.c | 2 +-
> drivers/gpu/drm/imagination/pvr_queue.c | 2 +-
> drivers/gpu/drm/lima/lima_sched.c | 2 +-
> drivers/gpu/drm/msm/msm_fence.c | 2 +-
> drivers/gpu/drm/nouveau/nouveau_fence.c | 4 +-
> drivers/gpu/drm/panfrost/panfrost_job.c | 2 +-
> drivers/gpu/drm/panthor/panthor_sched.c | 2 +-
> drivers/gpu/drm/qxl/qxl_release.c | 2 +-
> drivers/gpu/drm/radeon/radeon_fence.c | 2 +-
> drivers/gpu/drm/scheduler/sched_fence.c | 4 +-
> .../gpu/drm/scheduler/tests/mock_scheduler.c | 2 +-
> drivers/gpu/drm/ttm/tests/ttm_bo_test.c | 2 +-
> .../gpu/drm/ttm/tests/ttm_bo_validate_test.c | 2 +-
> drivers/gpu/drm/v3d/v3d_fence.c | 2 +-
> drivers/gpu/drm/vc4/vc4_gem.c | 2 +-
> drivers/gpu/drm/vgem/vgem_fence.c | 2 +-
> drivers/gpu/drm/virtio/virtgpu_fence.c | 2 +-
> drivers/gpu/drm/vmwgfx/vmwgfx_fence.c | 2 +-
> drivers/gpu/drm/xe/xe_hw_fence.c | 2 +-
> drivers/gpu/drm/xe/xe_oa.c | 2 +-
> drivers/gpu/drm/xe/xe_preempt_fence.c | 2 +-
> drivers/gpu/drm/xe/xe_tlb_inval.c | 2 +-
> drivers/gpu/host1x/fence.c | 2 +-
> drivers/iio/industrialio-buffer.c | 2 +-
> drivers/usb/gadget/function/f_fs.c | 2 +-
> include/linux/dma-fence.h | 14 +++--
> rust/kernel/dma_buf/dma_fence.rs | 2 +-
> 52 files changed, 95 insertions(+), 94 deletions(-)
>
>
> base-commit: 8258a37702b9b9cf27f5c0ea07625e3e6bd74f5a
prev parent reply other threads:[~2026-11-05 16:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 11:35 Philipp Stanner
2026-11-05 11:35 ` [PATCH 1/3] dma-buf: dma-fence: Add flags parameter to dma_fence_init() Philipp Stanner
2026-11-05 12:06 ` Tvrtko Ursulin
2026-11-05 12:35 ` Christian König
2026-11-05 12:48 ` Philipp Stanner
2026-11-05 14:23 ` Christian König
2026-11-05 12:51 ` Tvrtko Ursulin
2026-11-05 13:24 ` Philipp Stanner
2026-11-05 11:35 ` [PATCH 2/3] dma-buf: Port users of dma_fence_init64() Philipp Stanner
2026-11-05 11:35 ` [PATCH 3/3] dma-buf: dma-fence: Remove dma_fence_init64() Philipp Stanner
2026-11-05 16:32 ` Timur Kristóf [this message]
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=0e3689d102abf41b1e788402cc9da354d5c2d969.camel@gmail.com \
--to=timur.kristof@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=etnaviv@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=imagination@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=lima@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=phasta@kernel.org \
--cc=rust-for-linux@vger.kernel.or \
--cc=spice-devel@lists.freedesktop.org \
--cc=virtualization@lists.linux.dev \
/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®