From: Han Pingtian <hanpt@linux.vnet.ibm.com>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] questions about getrusage04
Date: Sat, 6 Dec 2014 09:24:22 +0800 [thread overview]
Message-ID: <20141206012422.GA3352@localhost.localdomain> (raw)
Hey,
I cannot understand why udelta/sdelta > "1000+(BIAS_MAX*factor_nr)" is a
problem. Could any expert give me a explain, please?
And looks like with this patch applied, it works well on powerpc:
diff --git a/testcases/kernel/syscalls/getrusage/getrusage04.c b/testcases/kernel/syscalls/getrusage/getrusage04.c
index 3640295..f118288 100644
--- a/testcases/kernel/syscalls/getrusage/getrusage04.c
+++ b/testcases/kernel/syscalls/getrusage/getrusage04.c
@@ -92,7 +92,7 @@ int main(int argc, char *argv[])
if (msg != NULL)
tst_brkm(TBROK, NULL, "OPTION PARSING ERROR - %s", msg);
-#if (__powerpc__) || (__powerpc64__) || (__s390__) || (__s390x__)
+#if (__s390__) || (__s390x__)
tst_brkm(TCONF, NULL, "This test is not designed for current system");
#endif
although the initial git comment said that "accuracy on powerpc
and s390x systems is always 10ms".
Thanks in advance!
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2014-12-06 5:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-06 1:24 Han Pingtian [this message]
2014-12-08 12:09 ` [LTP] questions about getrusage04 Cyril Hrubis
2014-12-08 13:03 ` Han Pingtian
2014-12-08 13:19 ` Cyril Hrubis
2014-12-08 13:52 ` Han Pingtian
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=20141206012422.GA3352@localhost.localdomain \
--to=hanpt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.