NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

kern/40612: timer_settime(2)'s ovalue is not relative time when the timer was created CLOCK_REALTIME

>Number:         40612
>Category:       kern
>Synopsis:       timer_settime(2)'s ovalue is not relative time when the timer 
>was created CLOCK_REALTIME
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Feb 11 11:00:00 +0000 2009
>Originator:     HITOSHI OSADA
>Release:        NetBSD 5.99.7
System: NetBSD amd690g 5.99.7 NetBSD 5.99.7 (AMD690G) #1: Sun Feb 8 00:53:26 
JST 2009 root@amd690g:/NetBSD-obj/src-obj/sys/arch/amd64/compile/AMD690G amd64
Architecture: x86_64
Machine: amd64

SUSv2( says

>The members of ovalue are subject to the resolution of the timer, and they are 
>same values that would be returned by a timer_gettime() call at that point in 


>The timer_gettime() function stores the amount of time until the specified 
> timerid, expires and the reload value of the timer into the space pointed to 
> by
> the value argument.
> This value is returned as the interval until timer expiration, even if the 
> timer
> was armed with absolute time.
but our timer_settime(2) always sets absolute time into ovalue when the timer 
was created as CLOCK_REALTIME.(CLOCK_VIRTUAL returns relative time correctly.)



Home | Main Index | Thread Index | Old Index