From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] ??? FAIL: Test report for kernel 5.4.0-rc6-dd89262.cki (mainline.kernel.org)
Date: Fri, 15 Nov 2019 10:52:34 +0100 [thread overview]
Message-ID: <20191115095234.GA18488@rei.lan> (raw)
In-Reply-To: <976393725.11648955.1573552572246.JavaMail.zimbra@redhat.com>
Hi!
> > perf_event_open02 again:
>
> I have a system [1] where it's consistently reproducible.
> It looks like count_hardware_counters() reports incorrect number.
> time_enabled and time_running are different but only barely (~0.7%).
>
> # ./perf_event_open02 -v
> at iteration:0 value:300357893 time_enabled:55368608 time_running:55368608
> at iteration:1 value:600712498 time_enabled:54808179 time_running:54403148
> perf_event_open02 0 TINFO : overall task clock: 54825931
> perf_event_open02 0 TINFO : hw sum: 1442538620, task clock sum: 260919342
> hw counters: 288507724 288507724 288507724 288507724 288507724
> task clock counters: 51773047 52526664 52531694 52540386 51547551
> perf_event_open02 0 TINFO : ratio: 4.759050
> perf_event_open02 1 TFAIL : perf_event_open02.c:394: test failed (ratio was greater than )
>
> Also do_work() completes pretty fast compared to a different host:
>
> real 0m0.176s
> user 0m0.163s
> sys 0m0.003s
I was thinking of setting up an CPU time alarm that would stop that loop
so that it will run for reasonably defined length regardless the CPU
speed...
--
Cyril Hrubis
chrubis@suse.cz
prev parent reply other threads:[~2019-11-15 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 8:05 [LTP] ❌ FAIL: Test report for kernel 5.4.0-rc6-dd89262.cki (mainline.kernel.org) CKI Project
2019-11-11 17:00 ` Jan Stancek
2019-11-12 9:56 ` Jan Stancek
2019-11-15 9:52 ` Cyril Hrubis [this message]
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=20191115095234.GA18488@rei.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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.