Support for select-like services.
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 of 4 patches 24 repliesIn review
3 of 4 patches are in this archive. The cover letter announces 4.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | nucleus core support for select-like services.nucleus/ nucleus/ nucleus/ +1 more | +542 | 0 replies | |
| 3/4 | posix skin kernel-space support for select.posix/ skins/ skins/ +4 more | +305 | 0 replies | |
| 4/4 | posix skin user-space support for select.posix/ skins/ skins/ +2 more | +60 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Xenomai-core] [patch 0/4] Support for select-like services.
Hi,
here comes a third edition of the patchset adding support for select.
The core support now depends on a CONFIG_XENO_OPT_SELECT option, whereas the posix support depends on a CONFIG_XENO_OPT_POSIX_SELECT option.
The support for using rtdm_event_t and rtdm_sem_t objects is now built-in to these objects without creating new objects types (only if CONFIG_XENO_OPT_SELECT is enabled).
The rtdm_context_get modification, allowing to check that the caller of a service belongs to the same process as the file descriptor it uses, is now made in __rtdm_context_get while rtdm_context_get passes a NULL first argument to this new service.
When implementing these modifications, a few questions arise:
- RTDM support currently depends on the CONFIG_XENO_OPT_SELECT option, should we add an RTDM specific option ?
- in order to avoid numerous #ifdefs, and especially in drivers code, the new callback added to device operations for binding RTDM file descriptors to selector blocks is always there even if CONFIG_XENO_OPT_SELECT is disabled. Is it the right thing to do ?
Regards.
Signature · 1 line
Gilles Chanteperdrix.