[PATCH] reservation: wait only with non-zero timeout specified (v3)

2015-01-21 Thread Maarten Lankhorst
Hey, Op 14-01-15 om 03:16 schreef Zhou, Jammy: >>> I think it would be best to leave timeout=0 returning 0. Not handling it >>> differently gives the same semantics as used by fence_wait_time and >>> wait_event_timeout. >>> Are there really many cases in which you don't know if timeout = 0 befor

[PATCH] reservation: wait only with non-zero timeout specified (v3)

2015-01-21 Thread Zhou, Jammy
] reservation: wait only with non-zero timeout specified (v3) Hey, Op 14-01-15 om 03:16 schreef Zhou, Jammy: >>> I think it would be best to leave timeout=0 returning 0. Not handling it >>> differently gives the same semantics as used by fence_wait_time and >>> wait_e

[PATCH] reservation: wait only with non-zero timeout specified (v3)

2015-01-14 Thread Zhou, Jammy
>> I think it would be best to leave timeout=0 returning 0. Not handling it >> differently gives the same semantics as used by fence_wait_time and >> wait_event_timeout. >> Are there really many cases in which you don't know if timeout = 0 before or >> not? >Yeah I think with this it's more imp

[PATCH] reservation: wait only with non-zero timeout specified (v3)

2015-01-13 Thread Daniel Vetter
On Tue, Jan 13, 2015 at 11:18:19AM +0100, Maarten Lankhorst wrote: > Op 13-01-15 om 10:22 schreef Christian König: > > Am 13.01.2015 um 10:04 schrieb Maarten Lankhorst: > >> Op 13-01-15 om 10:36 schreef Jammy Zhou: > >>> When the timeout value passed to reservation_object_wait_timeout_rcu > >>> is

[PATCH] reservation: wait only with non-zero timeout specified (v3)

2015-01-13 Thread Jammy Zhou
When the timeout value passed to reservation_object_wait_timeout_rcu is zero, no wait should be done if the fences are not signaled. Return '1' for idle and '0' for busy if the specified timeout is '0' to keep consistent with the case of non-zero timeout. v2: call fence_put if not signaled in the

[PATCH] reservation: wait only with non-zero timeout specified (v3)

2015-01-13 Thread Maarten Lankhorst
Op 13-01-15 om 10:22 schreef Christian König: > Am 13.01.2015 um 10:04 schrieb Maarten Lankhorst: >> Op 13-01-15 om 10:36 schreef Jammy Zhou: >>> When the timeout value passed to reservation_object_wait_timeout_rcu >>> is zero, no wait should be done if the fences are not signaled. >>> >>> Return

[PATCH] reservation: wait only with non-zero timeout specified (v3)

2015-01-13 Thread Christian König
Am 13.01.2015 um 10:04 schrieb Maarten Lankhorst: > Op 13-01-15 om 10:36 schreef Jammy Zhou: >> When the timeout value passed to reservation_object_wait_timeout_rcu >> is zero, no wait should be done if the fences are not signaled. >> >> Return '1' for idle and '0' for busy if the specified timeout

[PATCH] reservation: wait only with non-zero timeout specified (v3)

2015-01-13 Thread Maarten Lankhorst
Op 13-01-15 om 10:36 schreef Jammy Zhou: > When the timeout value passed to reservation_object_wait_timeout_rcu > is zero, no wait should be done if the fences are not signaled. > > Return '1' for idle and '0' for busy if the specified timeout is '0' > to keep consistent with the case of non-zero t

[PATCH] reservation: wait only with non-zero timeout specified (v3)

2015-01-13 Thread Zhou, Jammy
ou, Jammy; dri-devel at lists.freedesktop.org Cc: Deucher, Alexander; Koenig, Christian Subject: Re: [PATCH] reservation: wait only with non-zero timeout specified (v3) Op 13-01-15 om 10:36 schreef Jammy Zhou: > When the timeout value passed to reservation_object_wait_timeout_rcu > is zero, no wait