aboutsummaryrefslogtreecommitdiff
path: root/fdm.h (follow)
Commit message (Collapse)AuthorAgeLines
* fdm: add support for managing signalsDaniel Eklöf2021-02-11-2/+6
| | | | | | | | | | | | | | | | | | Add fdm_signal_add() and fdm_signal_del(). Signals added to the fdm will be monitored, and the provided callback called as “soon as possible” from the main context (i.e not from the signal handler context). Monitored signals are *blocked* by default. We use epoll_pwait() to unblock them while we’re polling. This allows us to do race-free signal detection. We use a single handler for all monitored signals; the handler simply updates the signal’s slot in a global array (sized to fit SIGRTMAX signals). When epoll_pwait() returns EINTR, we loop the global array. The callback associated with each signal that fired is called.
* fdm: add hook prioritiesDaniel Eklöf2020-01-04-2/+9
| | | | | | | | | | There are now three hook priorities: low, normal, high. High priority hooks are executed *first*. Normal next, and last the low priority hooks. The renderer's terminal refresh hook now runs as a normal priority hook.
* fdm: add support for hooksDaniel Eklöf2020-01-04-0/+4
| | | | | Hooks are functions executed just before going into a poll(). Or just after executing all FD handlers, if you like.
* fdm: add fdm_event_add() and fdm_event_del()Daniel Eklöf2019-11-02-0/+3
| | | | | These functions allow users to modify already registered FDs, to add or remove events they are interested in.
* fdm: don't free FD data that may be referenced by epoll return dataDaniel Eklöf2019-11-01-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It is perfectly possible, and legal, for a FDM handler to delete another handler. The problem however is when the epoll returned array of FD events contain the removed FD handler *after* the handler that removed it. That is, if the epoll returned array is: [FD=13, FD=37] and the handler for FD=13 removes FD=37, then given the current implementation, the FD user data (our handler callback etc) will point to a free:d address. Add support for this situation by deferring FD handler removal *when called from another handler*. This is done by "locking" the FDM struct before looping the handlers for FDs with events (and unlocking afterwards). In fdm_del(), we check if the FDM has been locked, in which case the FD is marked as deleted, and put on a deferred list. But not *actually* deleted. Meanwhile, in the FDM poll function, we skip calling handlers for marked-for-deletion FDs. Then, when all FDs have been processed, we loop the deferred list and finally deletes the FDs for real.
* fdm: use the FDM's poll loopDaniel Eklöf2019-10-27-0/+15