Re: [PATCH i-g-t 0/5] igt/kms: Make fence waiting explicit.

[Gustavo Padovan <gustavo@padovan.org>]

Hi Maarten,

2017-07-06 Maarten Lankhorst <maarten.lankhorst@linux.intel.com>:

> I wanted to make kms_atomic_transition pass, but the nonblocking modeset
> fencing tests were bogus.
> 
> This series changes the semantics for fencing slightly. It only keeps the out fences
> in pipe_obj->out_fence_fd, it's up to the test to decide what to do with it, which
> is probably just waiting on the fd or checking if it completed.
> 
> Maarten Lankhorst (5):
>   tests/kms_atomic_transition: Add test for plane completion ordering.
>   lib/kms: Handle fence interaction correctly WRT TEST_ONLY.
>   tests/kms_atomic_transition: Only request fence on enabled pipes
>   tests/kms_atomic_transition: Do not clear in-fences after atomic
>     commit.
>   igt/kms: Do not wait for fence completion during commit
> 
>  lib/igt_kms.c                 | 41 ++++++++----------
>  tests/kms_atomic_transition.c | 99 +++++++++++++++++++++++++++++++++----------
>  2 files changed, 95 insertions(+), 45 deletions(-)

This make fencing a lot cleaner.

For the whole series:

Acked-by: Gustavo Padovan <gustavo.padovan@collabora.com>

Gustavo

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx