public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/27398] x86: Improve testing false positive for tst-cpu-features-cpuinfo with bad hardware. Date: Tue, 18 Jan 2022 14:24:59 +0000 [thread overview] Message-ID: <bug-27398-131-mYTIee424w@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27398-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27398 H.J. Lu <hjl.tools at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |WAITING --- Comment #14 from H.J. Lu <hjl.tools at gmail dot com> --- (In reply to Carlos O'Donell from comment #12) > (In reply to H.J. Lu from comment #11) > > Created attachment 13910 [details] > > The v2 patch > > > > Please try this. > > Thanks HJ. > > My apologies, I made a mistake during testing, this still fails: > > [carlos@fedora ~]$ taskset --cpu-list 0,1 ~/build/glibc-review/testrun.sh > /home/carlos/build/glibc-review/elf/tst-cpu-features-cpuinfo-static; echo $? > > Checking HAS_CPU_FEATURE (HLE): > HAS_CPU_FEATURE (HLE): 1 > cpuinfo (hle): 0 > *** failure *** > > Checking HAS_CPU_FEATURE (RTM): > HAS_CPU_FEATURE (RTM): 1 > cpuinfo (rtm): 0 > *** failure *** These should be fixed by the v3 patch. > Likewise: > > [carlos@fedora ~]$ taskset --cpu-list 0,1 ~/build/glibc-review/testrun.sh > /home/carlos/build/glibc-review/string/tst-memchr-rtm; echo $? > error: ../sysdeps/x86/tst-string-rtm.h:63: TSX abort rate: 100.00% (3000 out > of 3000) > error: 1 test failures > 1 > [carlos@fedora ~]$ taskset --cpu-list 0,1 ~/build/glibc-review/testrun.sh > /home/carlos/build/glibc-review/string/tst-memchr-rtm; echo $? > 77 > > [carlos@fedora ~]$ taskset --cpu-list 0,1 > ~/build/glibc-review-i686/testrun.sh > /home/carlos/build/glibc-review-i686/string/tst-memchr-rtm; echo $? > 77 > [carlos@fedora ~]$ taskset --cpu-list 0,1 > ~/build/glibc-review-i686/testrun.sh > /home/carlos/build/glibc-review-i686/string/tst-memchr-rtm; echo $? > error: ../sysdeps/x86/tst-string-rtm.h:63: TSX abort rate: 100.00% (3000 out > of 3000) > error: 1 test failures > 1 This test is gated by static int do_test_1 (const char *name, unsigned int loop, int (*prepare) (void), int (*function) (void)) { if (!CPU_FEATURE_ACTIVE (RTM)) return EXIT_UNSUPPORTED; Can you find put why your processor isn't on the black list? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-01-18 14:25 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-12 4:44 [Bug libc/27398] New: Sporadic failures in tst-cpu-features-cpuinfo siddhesh at sourceware dot org 2021-02-12 4:52 ` [Bug libc/27398] " siddhesh at sourceware dot org 2021-02-12 9:46 ` [Bug libc/27398] x86: " fweimer at redhat dot com 2021-02-12 9:59 ` siddhesh at sourceware dot org 2021-02-12 13:45 ` hjl.tools at gmail dot com 2021-02-12 13:51 ` hjl.tools at gmail dot com 2021-02-12 14:00 ` siddhesh at sourceware dot org 2022-01-14 22:20 ` carlos at redhat dot com 2022-01-14 22:21 ` [Bug libc/27398] x86: Improve testing false positive for tst-cpu-features-cpuinfo with bad hardware carlos at redhat dot com 2022-01-14 22:26 ` hjl.tools at gmail dot com 2022-01-14 22:57 ` hjl.tools at gmail dot com 2022-01-14 22:57 ` hjl.tools at gmail dot com 2022-01-17 14:09 ` carlos at redhat dot com 2022-01-17 15:17 ` hjl.tools at gmail dot com 2022-01-17 15:17 ` hjl.tools at gmail dot com 2022-01-18 3:49 ` carlos at redhat dot com 2022-01-18 3:50 ` carlos at redhat dot com 2022-01-18 14:22 ` hjl.tools at gmail dot com 2022-01-18 14:24 ` hjl.tools at gmail dot com [this message] 2022-01-18 16:17 ` carlos at redhat dot com 2022-01-18 16:32 ` hjl.tools at gmail dot com 2022-01-18 16:35 ` carlos at redhat dot com 2022-01-18 16:38 ` carlos at redhat dot com 2022-01-18 22:21 ` cvs-commit at gcc dot gnu.org 2022-01-18 22:22 ` hjl.tools at gmail dot com 2022-01-25 18:19 ` carlos at redhat dot com 2022-01-25 18:41 ` hjl.tools at gmail dot com 2022-01-25 18:42 ` hjl.tools at gmail dot com 2022-01-26 19:30 ` carlos at redhat dot com 2022-02-01 13:54 ` cvs-commit at gcc dot gnu.org 2022-02-01 14:08 ` cvs-commit at gcc dot gnu.org 2022-02-01 15:26 ` cvs-commit at gcc dot gnu.org 2022-02-01 15:36 ` cvs-commit at gcc dot gnu.org 2022-02-01 15:59 ` cvs-commit at gcc dot gnu.org 2022-02-01 16:06 ` cvs-commit at gcc dot gnu.org 2022-02-01 17:16 ` cvs-commit at gcc dot gnu.org 2022-05-02 10:42 ` fweimer at redhat dot com
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=bug-27398-131-mYTIee424w@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).