wayland/src/event-loop.c, branch 1.0.2

Move ARRAY_LENGTH out of public headers

2012-10-19T21:08:38Z

Exporting unprefixed symbols is a pretty bad idea so don't do that. Instea of redefining it WL_ARRAY_LENGTH, we just move the define to our private header. The scanner generates code that uses ARRAY_LENGTH, but we can just make it count the number elements and emit an integer constant instead.

Change filedescriptor API to be thread safe

2012-10-11T00:59:00Z

The update callback for the file descriptors was always a bit awkward and un-intuitive. The idea was that whenever the protocol code needed to write data to the fd it would call the 'update' function. This function would adjust the mainloop so that it polls for POLLOUT on the fd so we can eventually flush the data to the socket. The problem is that in multi-threaded applications, any thread can issue a request, which writes data to the output buffer and thus triggers the update callback. Thus, we'll be calling out with the display mutex held and may call from any thread. The solution is to eliminate the udpate callback and just require that the application or server flushes all connection buffers before blocking. This turns out to be a simpler API, although we now require clients to deal with EAGAIN and non-blocking writes. It also saves a few syscalls, since the socket will be writable most of the time and most writes will complete, so we avoid changing epoll to poll for POLLOUT, then write and then change it back for each write.

event-loop: export wl_event_loop_dispatch_idle()

2012-09-12T16:28:54Z

When integrating the wayland event-loop into another event-loop, we currently have no chance of checking whether there are pending idle sources that have to be called. This patch exports the "dispatch_idle_sources()" call so other event loops can call this before going to sleep. This is what wl_event_loop_dispatch() currently does so we simply allow external event-loops to do the same now. To avoid breaking existing applications, we keep the call to dispatch_idle_sources() in wl_event_loop_dispatch() for now. However, if we want we can remove this later and require every application to call this manually. This needs to be discussed, but the overhead is negligible so we will probably leave it as it is. This finally allows to fully integrate the wayland-server API into existing event-loops without any nasty workarounds. Signed-off-by: David Herrmann

event-loop: remove dead code

2012-09-11T01:28:34Z

There is really no need to increment "n" if we never read the value. The do-while() loop overwrites the value before it is read the first time. Signed-off-by: David Herrmann

event-loop: Delete fd from epoll when removing event source

2012-05-08T14:42:42Z

Closing an fd will remove it from the epoll set only if it hasn't been dup'ed. In other words, the fd is only removed from epoll when all file descriptors referring to the open file has been close. We now dup fd for fd sources, so we need to use EPOLL_CTL_DEL directly now.

event-loop: Consolidate code for setting up new sources

2012-05-08T13:30:49Z

event-loop: fix conditional checking

2012-05-08T13:08:57Z

Introduced in: commit 80f4f0d5127ebc8d5e35969a29691cf61a79997d Author: Jonas Ådahl Date: Wed Mar 21 10:31:24 2012 +0100 Signed-off-by: Tiago Vignatti

os: wrap epoll_create

2012-04-25T06:37:42Z

Some system C libraries do not have epoll_create1() nor EPOLL_CLOEXEC, provide a fallback. Add tests for the wrapper. Signed-off-by: Pekka Paalanen

event-loop: Use two-step destruction of event loop sources.

2012-03-21T14:30:19Z

Instead of directly freeing an event source upon removal put it in a queue later handled by the event loop; either after a dispatch or upon event loop destruction. This is necessary to avoid already queued up event sources to be freed during some other dispatch callback, causing segmentation faults when the event loop later tries to handle an event from the freed source. Signed-off-by: Jonas Ådahl

event-loop: always do the post-dispatch check

2012-03-20T19:15:19Z

The post-dispatch check on wl_event_loop_dispatch() was not being run if epoll_wait returned 0 events, making the check unreliable.

Fix WL_EVENT_WRITEABLE typo

2011-12-29T03:51:34Z

event-loop: Fix idle handler dispatch corner case

2011-10-29T18:27:33Z

When the last idle handler queues another idle handler, we fail to dispatch that last handler. The wl_list_for_each_safe loop looks up the next pointer before running the handler, and at that point it points to the head of the list and the loop terminates. Instead, just loop until the list is empty.

event-loop: Quiet a few warnings

2011-08-12T20:25:18Z

There's no good error recovery possible in these cases though.

Rename source subdir from wayland to src

2011-08-12T20:25:14Z