public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Ramesh <rameshyr@linux.vnet.ibm.com>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] clock_settime03 test fails on kernel-2.6.32
Date: Mon, 30 Sep 2013 12:01:52 +0530	[thread overview]
Message-ID: <52491AD8.7080706@linux.vnet.ibm.com> (raw)

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

             reply	other threads:[~2013-09-30  6:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-30  6:31 Ramesh [this message]
2013-09-30  7:03 ` [LTP] clock_settime03 test fails on kernel-2.6.32 Jan Stancek
2013-09-30 12:59   ` Ramesh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52491AD8.7080706@linux.vnet.ibm.com \
    --to=rameshyr@linux.vnet.ibm.com \
    --cc=ltp-list@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox