Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 1195380[details]
Changelog between 20151017 and 20160814 versions
Description of problem:
A new version of cpuid package is available upstream - cpuid-20160814
http://www.etallen.com/cpuid.html
Please rebase cpuid package in RHEL7.4 to this version.
Version-Release number of selected component (if applicable):
Name : cpuid
Version : 20151017
Release : 4.el7
I have already tested the latest version. Everything is fine except for this minor issue for the newly added cpuinfo2cpuid utility. I have already reported it to the author and I hope to get it fixed in the upstream:
======================================================================
It's great that you have added cpuinfo2cpuid to the official release!
I have done quick test to compare the output when started with cpuinfo2cpuid and when using cpuid:
************************************************************
cpuinfo2cpuid < /proc/cpuinfo | cpuid -1 -f - > starting_with_cpuinfo2cpuid
cpuid -1 > plain_cpuid
************************************************************
There is a significant difference in "feature information" between the two outputs. Please see the attached files plain_cpuid and starting_with_cpuinfo2cpuid
I assume this cannot be really avoided since when starting with cpuinfo2cpuid this information is simply missing. However, perhaps cpuid could be updated to skip the feature information entirely when edx contains only zeroes? What do you think?
$ cpuinfo2cpuid < /proc/cpuinfo
CPU:
0x00000000 0x00: eax=0x00000001 ebx=0x756e6547 ecx=0x6c65746e edx=0x49656e69
0x00000001 0x00: eax=0x000306e4 ebx=0x00000000 ecx=0x00000000 edx=0x00000000
======================================================================