getcontext and setcontext don't handle extra CPU state added after their
ABIs were laid down. getcontextx and setcontextx do, however, so note that.
Add .Xr to sigreturn, and note the hazard there as well.
Sponsored by: Netflix
Details
Details
- Reviewers
kib
Diff Detail
Diff Detail
- Repository
- rG FreeBSD src repository
- Lint
Lint Skipped - Unit
Tests Skipped - Build Status
Buildable 55247 Build 52136: arc lint + arc unit
Event Timeline
Comment Actions
This makes an impression that sigreturn(2) does not handle extended CPU state, which is not true, at least on both 32 and 64bit x86.
And for me it is not clear what do you mean by 'though the kernel typically manages the ucontext_t'.
IMO it is better to explain that ucontext_t MD layout was fixed in times where more modern CPU registers files were not yet introduced, and this is the reason that the state cannot be embedded into ucontext_t without breaking ABI. Instead, we provide them out of structure with pointers ...