[PATCH 2/4] X event queue mutex

[Simon Thum]

Keith Packard wrote:
> Why does inserting events do anything but pull events from the kernel,
> insert them to the queue and update the sprite location on the screen?
> All event processing should happen in the main server thread; the only
> latency we're looking to reduce is the mouse->sprite update.
It's really not much: Middle button emu, translation/acceleration, ...
The point being their guts are exposed via input properties. Most cases
are trivial, which reads 'fairly safe given properly aligned writes are
atomic'. For the rest, there should be provisions (like suppressing
input processing) or a clear statement against complicated stuff in
props. At least, that's my opinion.