From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: sumit.semwal@linaro.org, thomas.hellstrom@linux.intel.com,
daniel.vetter@ffwll.ch, dri-devel@lists.freedesktop.org,
linux-media@vger.kernel.org, intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] Add warning for nesting dma_fence containers
Date: Fri, 4 Feb 2022 11:04:23 +0100 [thread overview]
Message-ID: <20220204100429.2049-1-christian.koenig@amd.com> (raw)
Hi everyone,
Since some operations can then lead to recursive handling nesting
dma_fence containers into each other is only allowed under some
restrictions.
dma_fence_array containers can be attached to dma_fence_chain
containers and dma_fence_chain containers by chaining them together.
In all other cases the individual fences should be extracted with
the appropriate iterators and added to the new containers
individually.
I've separated the i915 cleanup from this change since it is
generally a different functionality and the build bots complained
about some issues with those patches.
Most patches are already reviewd, but especially the first one still
needs an rb tag.
Please review and comment,
Christian.
next reply other threads:[~2022-02-04 13:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 10:04 Christian König [this message]
2022-02-04 10:04 ` [Intel-gfx] [PATCH 1/6] dma-buf: consolidate dma_fence subclass checking Christian König
2022-02-04 10:36 ` Thomas Hellström
2022-02-04 10:04 ` [Intel-gfx] [PATCH 2/6] dma-buf: warn about dma_fence_array container rules v2 Christian König
2022-02-04 10:04 ` [Intel-gfx] [PATCH 3/6] dma-buf: Warn about dma_fence_chain " Christian König
2022-02-09 14:02 ` Thomas Hellström
2022-02-09 14:42 ` Christian König
2022-02-04 10:04 ` [Intel-gfx] [PATCH 4/6] dma-buf: warn about containers in dma_resv object Christian König
2022-02-04 10:04 ` [Intel-gfx] [PATCH 5/6] dma-buf: add dma_fence_chain_contained helper Christian König
2022-02-04 10:38 ` Thomas Hellström
2022-02-04 10:04 ` [Intel-gfx] [PATCH 6/6] drm/amdgpu: use dma_fence_chain_contained Christian König
2022-02-04 15:43 ` Alex Deucher
2022-02-04 10:40 ` [Intel-gfx] Add warning for nesting dma_fence containers Thomas Hellström
2022-02-04 13:20 ` Christian König
2022-02-04 13:36 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/6] dma-buf: consolidate dma_fence subclass checking Patchwork
2022-02-04 13:38 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-02-04 14:16 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
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=20220204100429.2049-1-christian.koenig@amd.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-media@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=thomas.hellstrom@linux.intel.com \
/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