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

Op 07-07-17 om 02:15 schreef Gustavo Padovan: > Hi Maarten, > > 2017-07-06 Maarten Lankhorst : > >> I wanted to make kms_atomic_transition pass, but the nonblocking modeset >> fencing tests were bogus. >> >> This series changes the semantics for fencing slightly.

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

Hi Maarten, 2017-07-06 Maarten Lankhorst : > 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

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

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