* [LTP] clock_settime03 test fails on kernel-2.6.32
@ 2013-09-30 6:31 Ramesh
2013-09-30 7:03 ` Jan Stancek
0 siblings, 1 reply; 3+ messages in thread
From: Ramesh @ 2013-09-30 6:31 UTC (permalink / raw)
To: ltp-list
Hi All,
I am facing some issues with clock_settim03 test of timers group.
clock_settime03 evaluates
the error condition of clock_settime systemcall. On my machine, TEST8 &
TEST9 are failing as
the expeted error is not equal to the actual error.
After analysis, I found that the TEST8 & TEST9 are trying to
set CLOCK_PROCESS_CPUTIME_ID and CLOCK_THREAD_CPUTIME_ID respectively.
But from the man pages, it says that
"According to POSIX.1-2001, the CLOCK_PROCESS_CPUTIME_ID and
CLOCK_THREAD_CPUTIME_ID
clocks should be settable using clock_settime(). How-ever, the clocks
currently are not settable".
Also, in the below code snippet of
ltp/testcases/kernel/timers/clock_settime/clock_settime03.c
the if statement looks nothing for my kernel-2.6.32. So, the value of
testcases[7] and testcases[8]
will get assigned to EFAULT but actually both of them should get set to
EINVAL as the support is not
available on kernel-2.6.32.
-----------
/* PROCESS_CPUTIME_ID & THREAD_CPUTIME_ID are not supported on
* kernel versions lower than 2.6.12 and changed back in 2.6.38
*/
if ((tst_kvercmp(2, 6, 12)) < 0 || (tst_kvercmp(2, 6, 38)) >= 0) {
testcases[7] = EINVAL;
testcases[8] = EINVAL;
} else {
testcases[7] = EFAULT;
testcases[8] = EFAULT;
}
------------
I would like to know from which version onwards the
CLOCK_PROCESS_CPUTIME_ID and CLOCK_THREAD_CPUTIME_ID
clocks can be set using clock_settime() so that I can generate a valid
patch for this testcase.
Regards,
Ramesh
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [LTP] clock_settime03 test fails on kernel-2.6.32
2013-09-30 6:31 [LTP] clock_settime03 test fails on kernel-2.6.32 Ramesh
@ 2013-09-30 7:03 ` Jan Stancek
2013-09-30 12:59 ` Ramesh
0 siblings, 1 reply; 3+ messages in thread
From: Jan Stancek @ 2013-09-30 7:03 UTC (permalink / raw)
To: Ramesh; +Cc: ltp-list
----- Original Message -----
> From: "Ramesh" <rameshyr@linux.vnet.ibm.com>
> To: ltp-list@lists.sourceforge.net
> Sent: Monday, 30 September, 2013 8:31:52 AM
> Subject: [LTP] clock_settime03 test fails on kernel-2.6.32
>
> Hi All,
>
> I am facing some issues with clock_settim03 test of timers group.
> clock_settime03 evaluates
> the error condition of clock_settime systemcall. On my machine, TEST8 &
> TEST9 are failing as
> the expeted error is not equal to the actual error.
>
> After analysis, I found that the TEST8 & TEST9 are trying to
> set CLOCK_PROCESS_CPUTIME_ID and CLOCK_THREAD_CPUTIME_ID respectively.
> But from the man pages, it says that
> "According to POSIX.1-2001, the CLOCK_PROCESS_CPUTIME_ID and
> CLOCK_THREAD_CPUTIME_ID
> clocks should be settable using clock_settime(). How-ever, the clocks
> currently are not settable".
>
> Also, in the below code snippet of
> ltp/testcases/kernel/timers/clock_settime/clock_settime03.c
> the if statement looks nothing for my kernel-2.6.32. So, the value of
> testcases[7] and testcases[8]
> will get assigned to EFAULT but actually both of them should get set to
> EINVAL as the support is not
> available on kernel-2.6.32.
>
> -----------
>
> /* PROCESS_CPUTIME_ID & THREAD_CPUTIME_ID are not supported on
> * kernel versions lower than 2.6.12 and changed back in 2.6.38
> */
> if ((tst_kvercmp(2, 6, 12)) < 0 || (tst_kvercmp(2, 6, 38)) >= 0) {
> testcases[7] = EINVAL;
> testcases[8] = EINVAL;
> } else {
> testcases[7] = EFAULT;
> testcases[8] = EFAULT;
> }
>
> ------------
>
> I would like to know from which version onwards the
> CLOCK_PROCESS_CPUTIME_ID and CLOCK_THREAD_CPUTIME_ID
> clocks can be set using clock_settime() so that I can generate a valid
> patch for this testcase.
Hi,
what LTP version are you running?
Can you check if it has following commit:
https://github.com/linux-test-project/ltp/commit/a2d159595a761da1626b3f489dfe9cf2c351b774
Regards,
Jan
>
>
>
> Regards,
> Ramesh
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
>
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [LTP] clock_settime03 test fails on kernel-2.6.32
2013-09-30 7:03 ` Jan Stancek
@ 2013-09-30 12:59 ` Ramesh
0 siblings, 0 replies; 3+ messages in thread
From: Ramesh @ 2013-09-30 12:59 UTC (permalink / raw)
To: Jan Stancek, ltp-list
On 09/30/2013 12:33 PM, Jan Stancek wrote:
>
>
>
> ----- Original Message -----
>> From: "Ramesh" <rameshyr@linux.vnet.ibm.com>
>> To: ltp-list@lists.sourceforge.net
>> Sent: Monday, 30 September, 2013 8:31:52 AM
>> Subject: [LTP] clock_settime03 test fails on kernel-2.6.32
>>
>> Hi All,
>>
>> I am facing some issues with clock_settim03 test of timers group.
>> clock_settime03 evaluates
>> the error condition of clock_settime systemcall. On my machine, TEST8 &
>> TEST9 are failing as
>> the expeted error is not equal to the actual error.
>>
>> After analysis, I found that the TEST8 & TEST9 are trying to
>> set CLOCK_PROCESS_CPUTIME_ID and CLOCK_THREAD_CPUTIME_ID respectively.
>> But from the man pages, it says that
>> "According to POSIX.1-2001, the CLOCK_PROCESS_CPUTIME_ID and
>> CLOCK_THREAD_CPUTIME_ID
>> clocks should be settable using clock_settime(). How-ever, the clocks
>> currently are not settable".
>>
>> Also, in the below code snippet of
>> ltp/testcases/kernel/timers/clock_settime/clock_settime03.c
>> the if statement looks nothing for my kernel-2.6.32. So, the value of
>> testcases[7] and testcases[8]
>> will get assigned to EFAULT but actually both of them should get set to
>> EINVAL as the support is not
>> available on kernel-2.6.32.
>>
>> -----------
>>
>> /* PROCESS_CPUTIME_ID & THREAD_CPUTIME_ID are not supported on
>> * kernel versions lower than 2.6.12 and changed back in 2.6.38
>> */
>> if ((tst_kvercmp(2, 6, 12)) < 0 || (tst_kvercmp(2, 6, 38)) >= 0) {
>> testcases[7] = EINVAL;
>> testcases[8] = EINVAL;
>> } else {
>> testcases[7] = EFAULT;
>> testcases[8] = EFAULT;
>> }
>>
>> ------------
>>
>> I would like to know from which version onwards the
>> CLOCK_PROCESS_CPUTIME_ID and CLOCK_THREAD_CPUTIME_ID
>> clocks can be set using clock_settime() so that I can generate a valid
>> patch for this testcase.
> Hi,
>
> what LTP version are you running?
I am using may-2013 version of LTP.
Thanks for pointing to the fix, its available in Sep-2013 build.
Regards,
Ramesh
> Can you check if it has following commit:
> https://github.com/linux-test-project/ltp/commit/a2d159595a761da1626b3f489dfe9cf2c351b774
>
> Regards,
> Jan
>
>>
>>
>> Regards,
>> Ramesh
>>
>>
>> ------------------------------------------------------------------------------
>> October Webinars: Code for Performance
>> Free Intel webinars can help you accelerate application performance.
>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
>> the latest Intel processors and coprocessors. See abstracts and register >
>> http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Ltp-list mailing list
>> Ltp-list@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/ltp-list
>>
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-09-30 12:59 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-09-30 6:31 [LTP] clock_settime03 test fails on kernel-2.6.32 Ramesh
2013-09-30 7:03 ` Jan Stancek
2013-09-30 12:59 ` Ramesh
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox