Today
Just reverted instead, "may be" removed in 15.0 is good enough.
I think those issues are not made any worse by your patch? And the fix is something that RISC-V and amd64 would need as well (well, RISC-V also needs this patch). I think you should just merge your current patch and let @markj fix both amd64 and aarch64 when he adds the new arena.
Enable building the driver as a module.
BTW, I've thought about adding an acpi_unregister_ioctl_all or the like that just takes the fn argument and unregisters all commands that use the same function. That would be a nicer way to handle unloading of a module that registers multiple handlers.
Sorry to bring this back, but I'm noticing intermittency again on latest 16-CURRENT HEAD. I can reproduce it locally on amd64, and I'm seeing it fail on aarch64 in jenkins with the same result: https://ci.freebsd.org/view/Test/job/FreeBSD-main-aarch64-test/1857/testReport/sys.fs.fusefs/bad_server/main/
Ping.
This is a behavior change. I think it deserves a Relnotes: Yes commit meta message.
No longer applicable.
(for direct commit to stable/14)
Two different processes cannot have an opened descriptor to the same MIDI device. So, I think the only problematic case is when a process opens the device and a child thread is waiting in blocking mode; if the descriptor is closed by the parent thread, will this properly stop the blocking read?
Use hwpstate_amd instead of hwpstate
Not short-circuiting for cpu
See also the discussion in D47678 from when I implemented what looks like the same patch
More than 5, this is overdue