This is _really_ ugly.
Can't you just do this relaxation in "schedule_hrtimeout()" instead, and
just document the fact that the "high resolution" of hrtimeout is relative
to the length of the timeout.
It's not that select() doesn't care, it's that *NOBODY* cares. If somebody
asks for a timeout of one second and 2 microseconds, the two microseconds
simply don't matter. Ever. But if somebody asks for a timeout of 12
microseconds, individual microseconds probably _do_ matter.
So if you want high-resolution select/poll, then get rid of the "use_hr"
logic entirely, and just do it unconditionally. Then, relax the scheduler
timeouts in the scheduler.
(But, that's probably _generally_ true. Even now, when people do
"schedule_timeout()", there's a big difference between asking for two
ticks and asking for two seconds. The latter should probably try to round
to a nice timer tick basis for power reasons).
Linus
--
