From: Chunming Zhou <zhoucm1@amd.com>
To: "Koenig, Christian" <Christian.Koenig@amd.com>,
"Zhou, David(ChunMing)" <David1.Zhou@amd.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/syncobj: extend syncobj query ability
Date: Tue, 23 Jul 2019 14:07:25 +0000 [thread overview]
Message-ID: <d9ecceda-0ce2-341b-3f42-9202be302772@amd.com> (raw)
In-Reply-To: <1946e636-7c21-7456-3824-72a98c7305a4@amd.com>
在 2019/7/23 21:58, Koenig, Christian 写道:
> Am 23.07.19 um 07:22 schrieb Chunming Zhou:
>> user space needs a flexiable query ability.
>> So that umd can get last signaled or submitted point.
>>
>> Change-Id: I6512b430524ebabe715e602a2bf5abb0a7e780ea
>> Signed-off-by: Chunming Zhou <david1.zhou@amd.com>
>> Cc: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
>> Cc: Christian König <Christian.Koenig@amd.com>
> I've recently found a bug in drm_syncobj_query_ioctl() which I'm going
> to commit tomorrow.
Yes, I've realized. Loinel has put RB on it.
>
> Apart from that it looks good to me,
Thanks,
> but I think we should cleanup a bit
> and move the dma_fence_chain_for_each()... into a helper function in
> dma-fence-chain.c
Do you mind a saperate cleanup patch for that? I don't want to touch
kernel directory in this patch, so that we can cherry-pick it easily.
-David
>
> Christian.
>
>> ---
>> drivers/gpu/drm/drm_syncobj.c | 36 +++++++++++++++++------------------
>> include/uapi/drm/drm.h | 3 ++-
>> 2 files changed, 20 insertions(+), 19 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/drm_syncobj.c b/drivers/gpu/drm/drm_syncobj.c
>> index 3d400905100b..f70dedf3ef4f 100644
>> --- a/drivers/gpu/drm/drm_syncobj.c
>> +++ b/drivers/gpu/drm/drm_syncobj.c
>> @@ -1197,9 +1197,6 @@ drm_syncobj_timeline_signal_ioctl(struct drm_device *dev, void *data,
>> if (!drm_core_check_feature(dev, DRIVER_SYNCOBJ_TIMELINE))
>> return -EOPNOTSUPP;
>>
>> - if (args->pad != 0)
>> - return -EINVAL;
>> -
>> if (args->count_handles == 0)
>> return -EINVAL;
>>
>> @@ -1268,9 +1265,6 @@ int drm_syncobj_query_ioctl(struct drm_device *dev, void *data,
>> if (!drm_core_check_feature(dev, DRIVER_SYNCOBJ_TIMELINE))
>> return -EOPNOTSUPP;
>>
>> - if (args->pad != 0)
>> - return -EINVAL;
>> -
>> if (args->count_handles == 0)
>> return -EINVAL;
>>
>> @@ -1291,23 +1285,29 @@ int drm_syncobj_query_ioctl(struct drm_device *dev, void *data,
>> if (chain) {
>> struct dma_fence *iter, *last_signaled = NULL;
>>
>> - dma_fence_chain_for_each(iter, fence) {
>> - if (!iter)
>> - break;
>> - dma_fence_put(last_signaled);
>> - last_signaled = dma_fence_get(iter);
>> - if (!to_dma_fence_chain(last_signaled)->prev_seqno)
>> - /* It is most likely that timeline has
>> - * unorder points. */
>> - break;
>> + if (args->flags &
>> + DRM_SYNCOBJ_QUERY_FLAGS_LAST_SUBMITTED) {
>> + point = fence->seqno;
>> + } else {
>> + dma_fence_chain_for_each(iter, fence) {
>> + if (!iter)
>> + break;
>> + dma_fence_put(last_signaled);
>> + last_signaled = dma_fence_get(iter);
>> + if (!to_dma_fence_chain(last_signaled)->prev_seqno)
>> + /* It is most likely that timeline has
>> + * unorder points. */
>> + break;
>> + }
>> + point = dma_fence_is_signaled(last_signaled) ?
>> + last_signaled->seqno :
>> + to_dma_fence_chain(last_signaled)->prev_seqno;
>> }
>> - point = dma_fence_is_signaled(last_signaled) ?
>> - last_signaled->seqno :
>> - to_dma_fence_chain(last_signaled)->prev_seqno;
>> dma_fence_put(last_signaled);
>> } else {
>> point = 0;
>> }
>> + dma_fence_put(fence);
>> ret = copy_to_user(&points[i], &point, sizeof(uint64_t));
>> ret = ret ? -EFAULT : 0;
>> if (ret)
>> diff --git a/include/uapi/drm/drm.h b/include/uapi/drm/drm.h
>> index 661d73f9a919..fd987ce24d9f 100644
>> --- a/include/uapi/drm/drm.h
>> +++ b/include/uapi/drm/drm.h
>> @@ -777,11 +777,12 @@ struct drm_syncobj_array {
>> __u32 pad;
>> };
>>
>> +#define DRM_SYNCOBJ_QUERY_FLAGS_LAST_SUBMITTED (1 << 0) /* last available point on timeline syncobj */
>> struct drm_syncobj_timeline_array {
>> __u64 handles;
>> __u64 points;
>> __u32 count_handles;
>> - __u32 pad;
>> + __u32 flags;
>> };
>>
>>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-07-23 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 5:22 [PATCH] drm/syncobj: extend syncobj query ability Chunming Zhou
2019-07-23 13:58 ` Koenig, Christian
2019-07-23 14:07 ` Chunming Zhou [this message]
2019-07-23 14:08 ` Koenig, Christian
2019-07-30 12:00 ` Koenig, Christian
2019-07-23 14:06 ` Lionel Landwerlin
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=d9ecceda-0ce2-341b-3f42-9202be302772@amd.com \
--to=zhoucm1@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=David1.Zhou@amd.com \
--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