Hide Forgot
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 ======================================================================
Created attachment 1195382 [details] Log files for minor issue with cpuinfo2cpuid
Hi all, this is duplicate of this BZ: Bug 1381311 - [Intel 7.4 FEAT] Update cpuid package to version with support for Knights Mill https://bugzilla.redhat.com/show_bug.cgi?id=1381311 Jirka
*** This bug has been marked as a duplicate of bug 1381311 ***