History log of /external/ltp/testcases/kernel/syscalls/getrusage/getrusage04.c
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
d6d11d08678aac1ed2c370ea8e42e5f45aea07be 09-Mar-2015 Cyril Hrubis <chrubis@suse.cz> Introduce tst_parse_opts()

The pattern that was used in all testcases is:

const char *msg;

msg = parse_opts(...);
if (msg)
tst_brkm(TBROK, NULL, "OPTION PARSING ERROR - %s", msg);

This change simplifies the steps to just calling:

tst_parse_opts(...);

Signed-off-by: Cyril Hrubis <chrubis@suse.cz>
/external/ltp/testcases/kernel/syscalls/getrusage/getrusage04.c
e1ac3141303220b25171b79380ef230c02070e39 04-Feb-2015 Jiri Jaburek <jjaburek@redhat.com> getrusage04: skip on QEMU/kvm in addition to Xen

This test is unstable under QEMU as well, given the extra scheduling
on top of the virtual CPUs.

getrusage04 0 TINFO : utime: 0us; stime: 622us
getrusage04 0 TINFO : utime: 0us; stime: 1548us
getrusage04 0 TINFO : utime: 0us; stime: 2547us
getrusage04 0 TINFO : utime: 0us; stime: 3543us
getrusage04 0 TINFO : utime: 0us; stime: 4541us
getrusage04 0 TINFO : utime: 2770us; stime: 4541us
getrusage04 1 TFAIL : getrusage04.c:130: utime increased > 2000us:

Signed-off-by: Jiri Jaburek <jjaburek@redhat.com>
/external/ltp/testcases/kernel/syscalls/getrusage/getrusage04.c
aabb8340f63ed31afe995fd97795e542dc68b93c 04-Feb-2015 Cyril Hrubis <chrubis@suse.cz> Include usctest.h in test.h

Signed-off-by: Cyril Hrubis <chrubis@suse.cz>
/external/ltp/testcases/kernel/syscalls/getrusage/getrusage04.c
605fa3362fd7cef0baa2131be32cf44661783d3e 04-Feb-2015 Cyril Hrubis <chrubis@suse.cz> Get rid of TEST_CLEANUP

Special thanks to Coccinelle for making this easy job.

Signed-off-by: Cyril Hrubis <chrubis@suse.cz>
/external/ltp/testcases/kernel/syscalls/getrusage/getrusage04.c
0b9589f3f9c0345b29cfcf7da5a1253c708303eb 27-May-2014 Cyril Hrubis <chrubis@suse.cz> testcases: Constify char *msg variable.

The parse_opts() now returns const char * instead of char * this commit
fixes all warnings caused by the change.

Signed-off-by: Cyril Hrubis <chrubis@suse.cz>
/external/ltp/testcases/kernel/syscalls/getrusage/getrusage04.c
0647a00a218fbbb576eea69555eeaff8c8017b98 21-Nov-2013 Cyril Hrubis <chrubis@suse.cz> Add include/lapi/posix_clocks.h and make use of it

Signed-off-by: Cyril Hrubis <chrubis@suse.cz>
/external/ltp/testcases/kernel/syscalls/getrusage/getrusage04.c
c26dd371acbd490b57bf7804371fef065de764ca 17-Oct-2013 Jan Stancek <jstancek@redhat.com> getrusage04: skip it on Xen

Skip this test on Xen, as it is known to fail, presumably because
Xen is not able to account virtual CPU time with same accuracy
as on the real CPU.

Signed-off-by: Jan Stancek <jstancek@redhat.com>
Acked-by: Cyril Hrubis <chrubis@suse.cz>
/external/ltp/testcases/kernel/syscalls/getrusage/getrusage04.c
d59a659cd639ca2780b00049d102acd2a783d585 07-Mar-2013 Caspar Zhang <caspar@casparzhang.com> s/Tst_count/tst_count/ to avoid CamelCase

when using latest checkpatch.pl, CamelCase variables are not encouraged,
this patch does a batch update to replace all var `Tst_count` with
`tst_count`.

Signed-off-by: Caspar Zhang <caspar@casparzhang.com>
Acked-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
/external/ltp/testcases/kernel/syscalls/getrusage/getrusage04.c
07f4e5432dd3e7a60bc0235f13200640c82d8f89 21-Feb-2013 Cyril Hrubis <chrubis@suse.cz> syscalls/getrusage04: Try guess timer granularity.

This patch adds timer granularity detection for the testcase.

The granularity of getrusage timers depends on CONFIG_HZ kernel
parameter. There is unfortunately no API to get getrusage timers
resolution but there are linux specific POSIX timers that have exactly
same granularity. These are now used to detect the expected timers
resolution.

Signed-off-by: Cyril Hrubis <chrubis@suse.cz>
/external/ltp/testcases/kernel/syscalls/getrusage/getrusage04.c
354ebb48db8e66a853a58379a4808d5dcd1ceac3 07-Dec-2012 Wanlong Gao <gaowanlong@cn.fujitsu.com> cleanup code indent

Cleanup the code indent using:

find . -name *.c -exec Lindent {} \;

It's really a big change, but can fix almost all of
the indent problem in C code, although we can't
ensure all of the changes are right, but the error
changes are really few.

Signed-off-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
/external/ltp/testcases/kernel/syscalls/getrusage/getrusage04.c
46c552ee91f2f8273d1c0304f1a3438f65b8609f 07-Mar-2012 Jan Stancek <jstancek@redhat.com> getrusage04: initialise [us]last to current values

On slower machines, startup can take some time,
set last values to current [us]time before actual test.

This caused test to fail, because first delta contained
time spent by test starting up:
getrusage04 0 TINFO : utime: 999us; stime: 6998us
getrusage04 0 TINFO : utime: 999us; stime: 6998us
getrusage04 1 TFAIL : stime increased > 1000us: delta = 6998us

Signed-off-by: Jan Stancek <jstancek@redhat.com>
/external/ltp/testcases/kernel/syscalls/getrusage/getrusage04.c
fd875256d6f99102e3940c4dfc6b0a8a27f4d62c 23-Feb-2012 Filippo ARCIDIACONO <filippo.arcidiacono@st.com> getrusage04: add opportunity to increase the max [us]time increment

On slow systems it could be needed to increase the max value [us]time
increment beetween two getrusage calls.

Signed-off-by: Filippo Arcidiacono <filippo.arcidiacono@st.com>
Signed-off-by: Salvatore Cro <salvatore.cro@st.com>
/external/ltp/testcases/kernel/syscalls/getrusage/getrusage04.c
a88874be96ac732738981b5da32d49e8c75f7b1f 22-Dec-2011 Caspar Zhang <caspar@casparzhang.com> syscalls/getrusage04: new testcase

getrusage04 - accuracy of getrusage() with RUSAGE_THREAD

This program is used for testing the following upstream commit:
761b1d26df542fd5eb348837351e4d2f3bc7bffe.

getrusage() returns cpu resource usage with accuracy of 10ms
when RUSAGE_THREAD is specified to the argument who. Meanwhile,
accuracy is 1ms when RUSAGE_SELF is specified. This bad accuracy
of getrusage() caused a big impact on some application which is
critical to accuracy of cpu usage. The upstream fix removed
casts to clock_t in task_u/stime(), to keep granularity of
cputime_t over the calculation.

Note that the accuracy on powerpc and s390x systems is always
10ms when either RUSAGE_THREAD or RUSAGE_SELF specified, so
this test won't be executed on those platforms.

Signed-off-by: Caspar Zhang <caspar@casparzhang.com>
/external/ltp/testcases/kernel/syscalls/getrusage/getrusage04.c