Red Hat Bugzilla – Bug 1268604
Cannot use -p option for over-256 processor systems
Last modified: 2015-11-08 12:52:02 EST
Description of problem:
-p option is limited to processor number 255 intentionally but
nowadays, over-256 processor systems are coming.
Let's expand the max limit to, say, 65535 or more.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install msr-tools into a system that has 257 processors or more.
2. Use rdmsr command with "-p 256" option.
rdmsr exits with errno 127.
rdmsr should print the MSR value from CPU 256.
A sample fix is
Wouldn't we want a similar patch to wrmsr.c and cpuid.c? It looks like your pull request on github only addresses rdmsr.c.
(In reply to Greg Bailey from comment #1)
> Wouldn't we want a similar patch to wrmsr.c and cpuid.c? It looks like your
> pull request on github only addresses rdmsr.c.
You are correct. They are necessary.
I was wrong.
The value 65535 is nonsense because the variable is type of (int),
and also the theoretical max logical CPUs of RHEL7 is 5120.
So 5120 is enough here.
I was wrong again, 2,147,483,647 is the maximum of signed int for x86_64.
Still, 5120 is enough for RHEL7.
Greg, are you going to fix these three commands?
(In reply to Seiichi Ikarashi from comment #5)
> Greg, are you going to fix these three commands?
Yes, of course, I just returned from vacation and will address these either today or tomorrow.
msr-tools-1.3-3.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-ace89f67cb
msr-tools-1.3-3.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
$ su -c 'yum --enablerepo=epel-testing update msr-tools'
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-ace89f67cb
msr-tools-1.3-3.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.