From: Daniel Vetter <daniel@ffwll.ch>
To: "Christian König" <christian.koenig@amd.com>
Cc: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
dri-devel@lists.freedesktop.org, daniel.vetter@ffwll.ch
Subject: Re: [PATCH 03/23] dma-buf: add dma_resv_get_singleton v2
Date: Fri, 1 Apr 2022 17:57:57 +0200 [thread overview]
Message-ID: <YkchBXGnOvrD+jFw@phenom.ffwll.local> (raw)
In-Reply-To: <8e12de76-5206-81f8-0b8e-1c31865a7633@amd.com>
On Fri, Apr 01, 2022 at 10:21:22AM +0200, Christian König wrote:
> Daniel any more comments on this one here?
>
> It's the prerequisite to a bunch of other patches and I would like to get it
> out of my feet.
Apologies for the miss, I thought I've r-b stamped this one already.
>
> Thanks,
> Christian.
>
> Am 21.03.22 um 14:58 schrieb Christian König:
> > Add a function to simplify getting a single fence for all the fences in
> > the dma_resv object.
> >
> > v2: fix ref leak in error handling
> >
> > Signed-off-by: Christian König <christian.koenig@amd.com>
> > ---
> > drivers/dma-buf/dma-resv.c | 52 ++++++++++++++++++++++++++++++++++++++
> > include/linux/dma-resv.h | 2 ++
> > 2 files changed, 54 insertions(+)
> >
> > diff --git a/drivers/dma-buf/dma-resv.c b/drivers/dma-buf/dma-resv.c
> > index 5001e9b4420a..c09fd8da0c85 100644
> > --- a/drivers/dma-buf/dma-resv.c
> > +++ b/drivers/dma-buf/dma-resv.c
> > @@ -34,6 +34,7 @@
> > */
> > #include <linux/dma-resv.h>
> > +#include <linux/dma-fence-array.h>
> > #include <linux/export.h>
> > #include <linux/mm.h>
> > #include <linux/sched/mm.h>
> > @@ -650,6 +651,57 @@ int dma_resv_get_fences(struct dma_resv *obj, bool write,
> > }
> > EXPORT_SYMBOL_GPL(dma_resv_get_fences);
> > +/**
> > + * dma_resv_get_singleton - Get a single fence for all the fences
> > + * @obj: the reservation object
> > + * @write: true if we should return all fences
> > + * @fence: the resulting fence
> > + *
> > + * Get a single fence representing all the fences inside the resv object.
> > + * Returns either 0 for success or -ENOMEM.
> > + *
> > + * Warning: This can't be used like this when adding the fence back to the resv
> > + * object since that can lead to stack corruption when finalizing the
> > + * dma_fence_array.
Please add the standard boilerplate here:
Returns 0 on success and negative error values on failure.
> > + */
> > +int dma_resv_get_singleton(struct dma_resv *obj, bool write,
> > + struct dma_fence **fence)
> > +{
> > + struct dma_fence_array *array;
> > + struct dma_fence **fences;
> > + unsigned count;
> > + int r;
> > +
> > + r = dma_resv_get_fences(obj, write, &count, &fences);
Deep down in here we already have the dma_resv_assert_held, so I'm happy.
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> > + if (r)
> > + return r;
> > +
> > + if (count == 0) {
> > + *fence = NULL;
> > + return 0;
> > + }
> > +
> > + if (count == 1) {
> > + *fence = fences[0];
> > + kfree(fences);
> > + return 0;
> > + }
> > +
> > + array = dma_fence_array_create(count, fences,
> > + dma_fence_context_alloc(1),
> > + 1, false);
> > + if (!array) {
> > + while (count--)
> > + dma_fence_put(fences[count]);
> > + kfree(fences);
> > + return -ENOMEM;
> > + }
> > +
> > + *fence = &array->base;
> > + return 0;
> > +}
> > +EXPORT_SYMBOL_GPL(dma_resv_get_singleton);
> > +
> > /**
> > * dma_resv_wait_timeout - Wait on reservation's objects
> > * shared and/or exclusive fences.
> > diff --git a/include/linux/dma-resv.h b/include/linux/dma-resv.h
> > index 202cc65d0621..08512c1e215d 100644
> > --- a/include/linux/dma-resv.h
> > +++ b/include/linux/dma-resv.h
> > @@ -449,6 +449,8 @@ void dma_resv_replace_fences(struct dma_resv *obj, uint64_t context,
> > void dma_resv_add_excl_fence(struct dma_resv *obj, struct dma_fence *fence);
> > int dma_resv_get_fences(struct dma_resv *obj, bool write,
> > unsigned int *num_fences, struct dma_fence ***fences);
> > +int dma_resv_get_singleton(struct dma_resv *obj, bool write,
> > + struct dma_fence **fence);
> > int dma_resv_copy_fences(struct dma_resv *dst, struct dma_resv *src);
> > long dma_resv_wait_timeout(struct dma_resv *obj, bool wait_all, bool intr,
> > unsigned long timeout);
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2022-04-01 15:58 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 13:58 [PATCH 01/23] dma-buf: add dma_resv_replace_fences v2 Christian König
2022-03-21 13:58 ` [PATCH 02/23] dma-buf: finally make the dma_resv_list private v2 Christian König
2022-03-21 13:58 ` [PATCH 03/23] dma-buf: add dma_resv_get_singleton v2 Christian König
2022-04-01 8:21 ` Christian König
2022-04-01 15:57 ` Daniel Vetter [this message]
2022-03-21 13:58 ` [PATCH 04/23] RDMA: use dma_resv_wait() instead of extracting the fence Christian König
2022-03-23 13:22 ` Daniel Vetter
2022-03-23 16:32 ` Jason Gunthorpe
2022-03-23 17:34 ` Daniel Vetter
2022-03-21 13:58 ` [PATCH 05/23] drm/etnaviv: stop using dma_resv_excl_fence Christian König
2022-03-23 15:58 ` Lucas Stach
2022-03-21 13:58 ` [PATCH 06/23] drm/nouveau: " Christian König
2022-04-03 15:59 ` Christian König
2022-04-04 11:47 ` Karol Herbst
2022-04-05 7:25 ` Christian König
2022-03-21 13:58 ` [PATCH 07/23] drm/vmwgfx: " Christian König
2022-03-21 14:02 ` Zack Rusin
2022-03-21 14:12 ` Christian König
2022-03-21 15:11 ` Zack Rusin
2022-03-22 7:13 ` Christian König
2022-03-22 12:40 ` Zack Rusin
2022-03-21 13:58 ` [PATCH 08/23] drm/radeon: " Christian König
2022-03-21 13:58 ` [PATCH 09/23] drm/amdgpu: use dma_resv_for_each_fence for CS workaround Christian König
2022-03-21 13:58 ` [PATCH 10/23] dma-buf: finally make dma_resv_excl_fence private v2 Christian König
2022-03-23 13:36 ` Daniel Vetter
2022-04-05 7:58 ` Christian König
2022-03-21 13:58 ` [PATCH 11/23] dma-buf: drop the DAG approach for the dma_resv object v2 Christian König
2022-03-23 13:40 ` Daniel Vetter
2022-03-21 13:58 ` [PATCH 12/23] dma-buf/drivers: make reserving a shared slot mandatory v3 Christian König
2022-03-28 17:14 ` Daniel Vetter
2022-03-31 12:07 ` Christian König
2022-03-31 16:42 ` Daniel Vetter
2022-03-21 13:58 ` [PATCH 13/23] drm/atomic-helper: support more than one write fence in drm_gem_plane_helper_prepare_fb Christian König
2022-03-21 13:58 ` [PATCH 14/23] drm/nouveau: support more than one write fence in fenv50_wndw_prepare_fb Christian König
2022-03-21 13:58 ` [PATCH 15/23] drm/amdgpu: use dma_resv_get_singleton in amdgpu_pasid_free_cb Christian König
2022-03-21 13:58 ` [PATCH 16/23] dma-buf: add enum dma_resv_usage v3 Christian König
2022-03-29 15:24 ` Daniel Vetter
2022-04-04 1:13 ` Bas Nieuwenhuizen
2022-03-21 13:58 ` [PATCH 17/23] dma-buf: specify usage while adding fences to dma_resv obj v5 Christian König
2022-03-29 15:43 ` Daniel Vetter
2022-04-01 15:01 ` Christian König
2022-04-01 16:16 ` Daniel Vetter
2022-04-02 22:16 ` Bas Nieuwenhuizen
2022-04-03 17:48 ` Christian König
2022-03-21 13:58 ` [PATCH 18/23] drm/amdgpu: remove dma_resv workaround Christian König
2022-03-29 15:47 ` Daniel Vetter
2022-03-21 13:58 ` [PATCH 19/23] dma-buf: add DMA_RESV_USAGE_KERNEL v2 Christian König
2022-03-29 15:53 ` Daniel Vetter
2022-03-21 13:58 ` [PATCH 20/23] dma-buf: add DMA_RESV_USAGE_BOOKKEEP v2 Christian König
2022-03-29 16:06 ` Daniel Vetter
2022-03-21 13:58 ` [PATCH 21/23] dma-buf: wait for map to complete for static attachments Christian König
2022-03-29 15:56 ` Daniel Vetter
2022-03-21 13:58 ` [PATCH 22/23] drm/i915: drop bo->moving dependency Christian König
2022-03-29 15:57 ` Daniel Vetter
2022-03-21 13:58 ` [PATCH 23/23] drm/ttm: remove bo->moving Christian König
2022-03-29 16:02 ` Daniel Vetter
2022-04-05 9:25 ` Christian König
2022-04-05 12:51 ` Daniel Vetter
2022-03-21 14:03 ` [PATCH 01/23] dma-buf: add dma_resv_replace_fences v2 Christian König
2022-03-23 13:09 ` Daniel Vetter
2022-03-23 15:55 ` Felix Kuehling
2022-03-23 15:57 ` Christian König
-- strict thread matches above, loose matches on Subject: below --
2022-02-11 12:49 completely rework the dma_resv semantic Christian König
2022-02-11 12:49 ` [PATCH 03/23] dma-buf: add dma_resv_get_singleton v2 Christian König
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=YkchBXGnOvrD+jFw@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=christian.koenig@amd.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
/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