> and probably get it into a state where the existing getitimer/setitimer
> code can be removed and reimplemented on top of this new API.

We generally avoid that approach, because it makes it very difficult for
people to read ktrace output and reason about what software is actually
doing.