diff options
author | Matthew Waters <matthew@centricular.com> | 2016-03-18 17:17:23 +1100 |
---|---|---|
committer | Matthias Clasen <mclasen@redhat.com> | 2016-05-19 12:10:07 -0400 |
commit | 246385a8e7a435acd0c854aa43912352eb104acb (patch) | |
tree | f1f48e453677f4b94ef4e090fc1ba7cbb6df8986 /gdk/wayland/gdkscreen-wayland.c | |
parent | 1e2bde6971d68cf7a8eec972dbde85d3492e4086 (diff) | |
download | gtk+-246385a8e7a435acd0c854aa43912352eb104acb.tar.gz |
gdk/wayland: use the multi-thread safe wayland API
This is required for proper integration with any other library/application that
may perform wayland API calls and poll() the wayland fd from multiple threads.
Using wl_display_dispatch{_queue}() is thread-safe if not mixed with custom
poll() usage, which GSource/GMainContext does.
Essentially, the problem is that multiple threads polling and reading
the same fd is extremely racy. Use the wayland provided API for allowing
concurrent access to the wayland display fd.
See the wayland man pages for wl_display_prepare_read(),
wl_display_cancel_read() and wl_display_read_events() for more details.
https://bugzilla.gnome.org/show_bug.cgi?id=763852
Diffstat (limited to 'gdk/wayland/gdkscreen-wayland.c')
0 files changed, 0 insertions, 0 deletions