From: zhoucm1 <zhoucm1@amd.com>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
dri-devel@lists.freedesktop.org
Cc: daniel.vetter@ffwll.ch
Subject: Re: [PATCH 7/7] drm/syncobj: use the timeline point in drm_syncobj_find_fence
Date: Thu, 22 Nov 2018 14:52:53 +0800 [thread overview]
Message-ID: <7857f8af-7046-66a4-e679-3e788b5750c1@amd.com> (raw)
In-Reply-To: <20181115111245.30161-8-christian.koenig@amd.com>
On 2018年11月15日 19:12, Christian König wrote:
> Implement finding the right timeline point in drm_syncobj_find_fence.
>
> Signed-off-by: Christian König <christian.koenig@amd.com>
> ---
> drivers/gpu/drm/drm_syncobj.c | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/drm_syncobj.c b/drivers/gpu/drm/drm_syncobj.c
> index 589d884ccd58..d42c51520da4 100644
> --- a/drivers/gpu/drm/drm_syncobj.c
> +++ b/drivers/gpu/drm/drm_syncobj.c
> @@ -307,9 +307,17 @@ int drm_syncobj_find_fence(struct drm_file *file_private,
> return -ENOENT;
>
> *fence = drm_syncobj_fence_get(syncobj);
> - if (!*fence) {
> + if (!*fence)
> ret = -EINVAL;
> +
> + if (!ret && point) {
> + dma_fence_chain_for_each(*fence) {
> + if (!to_dma_fence_chain(*fence) ||
> + (*fence)->seqno <= point)
> + break;
This condition isn't enough to find proper point.
For two examples:
a. No garbage collection happens, the points in chain are
1----3----6----9----12---18---20, if user wants to get point17, then we
should return node 18.
b. garbage collection happens on point6, chain would be updated to
1---3---9---12---18---20, if user wants to get point5, then we should
return node 3, but if user wants to get point 7, then we should return
node 9.
I still have no idea how to satisfy all these requirements with your
current chain-fence. All these logic just are same we encountered
before, we're walking them again. After solving these problems, I guess
all design is similar as before.
In fact, I don't know what problem previous design has, maybe there are
some bugs, can't we fix these bugs by time going? Who can make sure his
implementation never have bugs?
-David
> + }
> }
> +
> drm_syncobj_put(syncobj);
> return ret;
> }
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-11-22 6:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 11:12 restart syncobj timeline changes Christian König
2018-11-15 11:12 ` [PATCH 1/7] dma-buf: make fence sequence numbers 64 bit Christian König
2018-11-16 5:26 ` Zhou, David(ChunMing)
2018-11-15 11:12 ` [PATCH 2/7] dma-buf: add new dma_fence_chain container Christian König
2018-11-16 5:51 ` Zhou, David(ChunMing)
2018-11-15 11:12 ` [PATCH 3/7] drm: revert "expand replace_fence to support timeline point v2" Christian König
2018-11-15 11:12 ` [PATCH 4/7] drm/syncobj: use only a single stub fence Christian König
2018-11-16 5:54 ` Zhou, David(ChunMing)
2018-11-15 11:12 ` [PATCH 5/7] drm/syncobj: move drm_syncobj_cb into drm_syncobj.c Christian König
2018-11-16 5:55 ` Zhou, David(ChunMing)
2018-11-15 11:12 ` [PATCH 6/7] drm/syncobj: add new drm_syncobj_add_point interface Christian König
2018-11-16 6:20 ` Zhou, David(ChunMing)
2018-11-15 11:12 ` [PATCH 7/7] drm/syncobj: use the timeline point in drm_syncobj_find_fence Christian König
2018-11-22 6:52 ` zhoucm1 [this message]
2018-11-22 11:30 ` Christian König
2018-11-23 2:36 ` zhoucm1
2018-11-23 10:10 ` Koenig, Christian
2018-11-23 10:56 ` zhoucm1
2018-11-23 11:03 ` Christian König
2018-11-23 12:02 ` Koenig, Christian
2018-11-23 12:26 ` Daniel Vetter
2018-11-23 12:40 ` Christian König
2018-11-27 7:53 ` Daniel Vetter
2018-11-23 13:15 ` Chunming Zhou
2018-11-23 13:27 ` Koenig, Christian
2018-11-23 13:42 ` Chunming Zhou
2018-11-23 18:16 ` Christian König
2018-11-24 8:28 ` Chunming Zhou
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=7857f8af-7046-66a4-e679-3e788b5750c1@amd.com \
--to=zhoucm1@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.