Page MenuHomeFreeBSD

umtx: Expose some of the umtx structures and API to the rest of the kernel.
ClosedPublic

Authored by dchagin on Jul 20 2021, 2:08 PM.
Tags
None
Referenced Files
F157013108: D31233.id92516.diff
Sun, May 17, 11:08 PM
F157013011: D31233.id92926.diff
Sun, May 17, 11:07 PM
F157013001: D31233.id92488.diff
Sun, May 17, 11:07 PM
F157009831: D31233.diff
Sun, May 17, 10:48 PM
Unknown Object (File)
Thu, May 7, 6:00 AM
Unknown Object (File)
Wed, May 6, 2:56 AM
Unknown Object (File)
Thu, Apr 30, 6:10 PM
Unknown Object (File)
Mon, Apr 27, 8:45 PM
Subscribers

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

I do not object against the idea of making more guts of kern_umtx.c usable for e.g. Linuxolator, but I think that polluting sys/umtx.h is not a right approach. I suggest to follow established practice, and add a new header, e.g. sys/umtxvar.h, where most of the stuff you moved could land.

More, I think that ideally you would move all the #ifdef _KERNEL bits from umtx.h to umtxvar.h, leaving umtx.h as ABI header for userspace.

Does it make sense?

sys/sys/umtx.h
187 ↗(On Diff #92488)

This is too generic name to expose in the reusable header. Please name it e.g. umtx_abs_timeout().

This revision was not accepted when it landed; it landed in state Needs Review.Jul 29 2021, 9:46 AM
This revision was automatically updated to reflect the committed changes.