Hide Forgot
Description of problem: Platform stress software and CPUID software are reading cache information via CPUID and find this bad descriptor: Type of cache Unified Cache Cache Level 0 Cache Level can't be 0 if cache type is non-zero. Version-Release number of selected component (if applicable): How reproducible: Easily on Linux or Windows guest OS. Steps to Reproduce: 1. Boot guest OS via KVM 2. Check CPUID cache descriptors x86info -c seems to ignore the bad descriptor, so use something else Actual results: Type of cache Unified Cache Cache Level 0 Expected results: Type of cache = 0 Additional info:
(In reply to comment #0) > Description of problem: > Platform stress software and CPUID software are reading cache information via > CPUID and find this bad descriptor: > > Type of cache Unified Cache > Cache Level 0 > > Cache Level can't be 0 if cache type is non-zero. Hi,thomas Would you please tell me which tool you used to read cache information and found bad descriptor?I tried cup-z & CPUID TMonitor.failed to get infos what you de scripted.thanks
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
We don't have the option to configure the cache bits with the current cpu model design. We'll need the complete cpu-type infrastructure planned for RHEL7 (bug 824991) in order to properly fix this. So deferring to RHEL7.
I can't locate the issue in the code and there's not enough information to reproduce the bug. Even the older RHEL-6 code looks correct and has level=2 in the only CPUID entry where cache type is 3 (unified cache).