From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] ❌ FAIL: Test report for kernel 5.4.0-rc6-dd89262.cki (mainline.kernel.org)
Date: Tue, 12 Nov 2019 04:56:12 -0500 (EST) [thread overview]
Message-ID: <976393725.11648955.1573552572246.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <232041279.11531466.1573491604178.JavaMail.zimbra@redhat.com>
----- Original Message -----
>
> ----- Original Message -----
> > ? LTP lite
>
> 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
[1]
# lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 36 bits physical, 48 bits virtual
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 2
Core(s) per socket: 1
Socket(s): 2
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 15
Model: 3
Model name: Intel(R) Xeon(TM) CPU 3.40GHz
Stepping: 4
CPU MHz: 2800.000
CPU max MHz: 3400.0000
CPU min MHz: 2800.0000
BogoMIPS: 6800.62
L1d cache: 32 KiB
L2 cache: 2 MiB
NUMA node0 CPU(s): 0-3
Vulnerability L1tf: Mitigation; PTE Inversion
Vulnerability Mds: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable
Vulnerability Meltdown: Mitigation; PTI
Vulnerability Spec store bypass: Vulnerable
Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2: Mitigation; Full generic retpoline, STIBP disabled, RSB filling
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall lm constant_tsc pebs bts nopl cpui
d pni dtes64 monitor ds_cpl est tm2 cid xtpr pti
next prev parent reply other threads:[~2019-11-12 9:56 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 [this message]
2019-11-15 9:52 ` [LTP] ??? " Cyril Hrubis
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=976393725.11648955.1573552572246.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox