- 4e94765 Timer related syscalls for LTP test: Signed-off-by: Suzuki K P <suzuki@in.ibm.com>, by Subrata Modak · 14 years ago
- c98956b The MAX_CLOCKS supported by the kernel is 16. But the kernel may not have all the clock sources defined in the range 0-15. Hence, to test whether kernel returns error for an INVALID clock source id, we should use the upper limit MAX_CLOCKS (16 at the moment). But to verify the the defined clocks work fine, we should loop through the "list" of clock sources defined for sure. MAX_CLOCKS marsk the end of the clock sources in the array. by Subrata Modak · 14 years ago
- a15d642 Add fud for CLOCK_MONOTONIC_RAW, even though (FWIW) it doesn't work on by Garrett Cooper · 14 years ago
- 917b2f9 Include definitions for CLOCK_MONOTONIC_COARSE and CLOCK_REALTIME_COARSE by Garrett Cooper · 14 years ago
- 1a7f542 Wholesale testcase cleanup. by yaberauneya · 15 years ago
- 0bd2fa8 In reference to the issue with timer_create04 and clock_gettime03 for the kernel version 2.6.29 which was reported in the link: http://www.nabble.com/timer_create-p22376043.html, PFA the patch for fixing the issue. Detail on the issue: A new clockid 'CLOCK_MONOTONIC_RAW' was added since the kernel 2.6.28 (http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.28). This addition caused the above testcases to fail. Now, 5 clock ID's are resent in kernel ver 2.6.28 and later. Signed-off-by: Rohit Verma <rohit.170309@gmail.com>. by subrata_modak · 15 years ago
- e8af978 CLOCK_PROCESS_CPUTIME_ID and CLOCK_THREAD_CPUTIME_ID are also supported besides CLOCK_REALTIME and CLOCK_MONOTONIC. That's the cause of the failure of clock_gettime03, timer_create02 and timer_create04. Another cause is that struct sigevent evp is assigned with invalid values when option is 1. That's the cause of the failure of timer_create02 and timer_create03. CLOCK_REALTIME_HR and CLOCK_MONOTONIC_HR have been removed in the later kernel versions, hence the failures in the test. I am still trying to find out if any kernel versions used to support these. CLOCK_PROCESS_CPUTIME_ID and CLOCK_THREAD_CPUTIME_ID are supported from 2.6.12 kernel version onwards and the test case needs to be modified for this change. Also in timer_create02.c, setup_test() case1 needs to be modified so as to make evp NULL instead of its members. Since the testcase behaves differently for different kernel versions, a version check needs to be added for making it pass across versions. I'm removing the HR clocks from the tests along with other changes, by, Anoop V. Chakkalakkal <anoop.vijayan@in.ibm.com> by subrata_modak · 16 years ago
- 9cf96d8 use common header for __NR defines by vapier · 18 years ago
- a9a1847 take some fixes from Yi CDL Yang and create a CLOCK list for people to use as well as a func to turn a clock value into a string by vapier · 18 years ago
- bc8a461 move common defines/functions/etc... to one header file so we have to get it right just once by vapier · 18 years ago
- 0b70c6e *** empty log message *** by robbiew · 21 years ago
- ebc87a7 Added neccessary include file for the high res timers tests. by robbiew · 21 years ago