![]() | ||||||||||
Messages in this thread |
Hi Thomas, I switched my custom kernel timer to use the ktimers with the prio of -1 as you mentioned to me offline. I set up the timer to be monotonic and have a requirement that the returned time is always greater or equal to the last time returned from do_get_ktime_mono. Now here's the results that I got between two calls of do_get_ktime_mono 358.069795728 secs then later 355.981483177. Should this ever happen? I haven't look to see if this happens in vanilla -rt10 but I haven't touched your ktimer code except for my logging and the patch with the unlock_ktimer_base (since I was based off of -rt9) FYI, the system is UP. And I compiled without CONFIG_KTIME_SCALAR. Thanks -- Steve - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | |||||||||
| Last update: 2005-10-19 15:02 [from the cache] ©2003-2008 | ||||||||||