From: Chunming Zhou <zhoucm1@amd.com>
To: "Zhou, David(ChunMing)" <David1.Zhou@amd.com>,
Chris Wilson <chris@chris-wilson.co.uk>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/syncobj: return meaningful value to user space
Date: Thu, 18 Jul 2019 13:24:34 +0000 [thread overview]
Message-ID: <f16a7452-965a-9934-3a74-3a7e7b42c1cf@amd.com> (raw)
In-Reply-To: <e38b9278-21d7-d4d5-0362-0c63b9f4a6aa@amd.com>
在 2019/7/18 21:15, Zhou, David(ChunMing) 写道:
> 在 2019/7/18 21:10, Chris Wilson 写道:
>> Quoting Chunming Zhou (2019-07-18 14:04:09)
>>> 在 2019/7/18 19:18, Chris Wilson 写道:
>>>> Quoting Chunming Zhou (2019-07-18 12:13:39)
>>>>> if WAIT_FOR_SUBMIT isn't set and in the meanwhile no underlying fence on syncobj,
>>>>> then return non-block error code to user sapce.
>>>> Block device required?
>>> Yes, if WAIT_FOR_SUBMIT is set, then that will block device.
>> No, the error message is that it requires a "block device", not that it
>> will block the device, which is EWOULDBLOCK.
Ah, I think I don't want EWOULDBLOCK, which will try again and again
ioctl, that is not my movitation.
I just need a meaningful value to identify the underlying fence isn't
ready on syncobj.
Because it is in 'else' case, ENOTBLK is correct to say here need block
but WAIT_FOR_SUBMIT isn't set.
-David
> OK, I got your mean.
>
> Any other possile value suggestted?
>
> -David
>
>> -Chris
_______________________________________________
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-18 13:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 11:13 [PATCH] drm/syncobj: return meaningful value to user space Chunming Zhou
2019-07-18 11:18 ` Chris Wilson
2019-07-18 13:04 ` Chunming Zhou
2019-07-18 13:10 ` Chris Wilson
2019-07-18 13:15 ` Chunming Zhou
2019-07-18 13:23 ` Chris Wilson
2019-07-18 13:24 ` Chunming Zhou [this message]
2019-07-18 11:31 ` Lionel Landwerlin
2019-07-18 13:02 ` Chunming Zhou
2019-07-18 14:08 ` Lionel Landwerlin
2019-07-18 14:33 ` Chunming Zhou
2019-07-19 8:13 ` Lionel Landwerlin
2019-07-19 8:31 ` zhoucm1
2019-07-22 8:46 ` Lionel Landwerlin
2019-07-22 10:11 ` zhoucm1
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=f16a7452-965a-9934-3a74-3a7e7b42c1cf@amd.com \
--to=zhoucm1@amd.com \
--cc=David1.Zhou@amd.com \
--cc=chris@chris-wilson.co.uk \
--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