RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1713658 - valgrind does not recognise rdrand and f16c instructions on machines without avx2
Summary: valgrind does not recognise rdrand and f16c instructions on machines without ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: valgrind
Version: 8.1
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Mark Wielaard
QA Contact: Alexandra Petlanová Hájková
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-24 12:25 UTC by Alexandra Petlanová Hájková
Modified: 2021-09-17 14:44 UTC (History)
3 users (show)

Fixed In Version: valgrind-3.15.0-9.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 20:51:51 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 408009 0 None None None 2019-05-27 23:09:48 UTC
Red Hat Product Errata RHEA-2019:3346 0 None None None 2019-11-05 20:51:55 UTC

Description Alexandra Petlanová Hájková 2019-05-24 12:25:06 UTC 
valgrind does not recognise rdrand and f16c instructions on machines without avx2 which makes none/tests/amd64/f16c and none/tests/amd64/rdrand tests fail

rpm -q valgrind
valgrind-3.15.0-4.el8.x86_64

/vg-in-place -v none/tests/amd64/rdrand 2>&1 | grep -i hwcaps
--6458-- Arch and hwcaps: AMD64, LittleEndian, amd64-cx16-rdtscp-sse3-ssse3-avx
Comment 1 Mark Wielaard 2019-05-24 15:54:20 UTC 
This caused by the following code in machine_get_hwcaps () coregrind/m_machine.c:

     /* Sanity check for RDRAND and F16C.  These don't actually *need* AVX2, but
        it's convenient to restrict them to the AVX2 case since the simulated
        CPUID we'll offer them on has AVX2 as a base. */
     if (!have_avx2) {
        have_f16c   = False;
        have_rdrand = False;
     }

This is somewhat lame. It could be argued that this is a testsuite bug, because it checks for support of f16c and rdrand on the host instead of under valgrind itself. But there really is no reason valgrind couldn't support f16c and rdrand in this case. It would need some surgery to the cpuid emulation code though.
Comment 2 Mark Wielaard 2019-05-27 23:09:48 UTC 
Fix proposed upstream: https://bugs.kde.org/show_bug.cgi?id=408009
Comment 4 Alexandra Petlanová Hájková 2019-06-03 10:12:35 UTC 
I verified rdrand and fc16 tests passes on machines with avx (without avx2) which supports rdrand and f16c instructions and are skipped and instread of failing on machines with avx or avx2 when the machine does not support such instructions.
Comment 6 errata-xmlrpc 2019-11-05 20:51:51 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:3346
Note You need to log in before you can comment on or make changes to this bug.