Use non-blocking timerfd to prevent blocking when updating timer event sources
Use non-blocking timerfd to prevent blocking when updating timer event sources

This implements a simple fix for the blocking problem that occurs when
updating a timer event source after the timer expires, but before its
callback is dispatched. This can happen when another event happens during the
same epoll wakeup as the timer event, and causes the read() call in
wl_event_source_timer_dispatch() to block for the updated duration of the
timer.

We never want this read() call to block, so I believe it makes sense for the
timerfd to be non-blocking, and we simply ignore the case where the read fails
with EAGAIN. We still report all other errors as before, and still ignore the
actual value read from the socket.

With this change, the event_loop_timer_updates unit test case I submitted
previously now passes, and weston appears to work as before.

abooij/wayland,sir-murray/wayland,sir-murray/wayland,abooij/wayland,bitfactor/wayland,mchalupa/wayland,mchalupa/wayland,bitfactor/wayland,sir-murray/wayland,mchalupa/wayland,eyolfson/wayland,tulcod/wayland,eyolfson/wayland,tulcod/wayland,bitfactor/wayland,eyolfson/wayland,tulcod/wayland,abooij/wayland