Defect report from : Michael Kerrisk , Linux Foundation
(Please direct followup comments direct to austin-group-l@xxxxxx)
@ page 2114 line 66945 section timer_getoverrun() comment {timer_getoverrun}
Problem:
Edition of Specification (Year): 2008
Defect code : 2. Omission
The discussion of timer overruns in lines 66945 to 66956
is phrased entirely in terms of timer notification via
signals (SIGEV_SIGNAL). However, a timer overrun can also
occur for for notification via a thread (SIGEV_THREAD),
since there may be a delay between the timer expiration
and the invocation of the corresponding thread, and in
that time, further expirations may occur. Linux, at
least, supports timer_getoverrun() in the context of
timer notification via a thread, and perhaps other
systems also do. I suspect the standard should say
something about this, an that it may be an accident of
history that it doesn't.
Action:
After line 66956, add text something like the following:
An implementation may also support the use of
timer_gettoverrun() for retrieving the overrun count
when timer expirations are notified via invocation of
a thread (SIGEV_THREAD). In this case, the overrun
count reflects the number of extra timer expirations
that have occurred between the first timer expiration
and the time that the notification thread was invoked.
|