Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

i7-920 incorrectly recognized as Haswell #19

Open
James-E-A opened this issue Jan 2, 2017 · 1 comment
Open

i7-920 incorrectly recognized as Haswell #19

James-E-A opened this issue Jan 2, 2017 · 1 comment

Comments

@James-E-A
Copy link

James-E-A commented Jan 2, 2017

Title says it all: I have a machine with an i7-920 (Bloomfield line / Nehalem microarchitecture), which i7z "guesses" is the Haswell architecture:

$ sudo i7z
i7z DEBUG: i7z version: svn-r93-(27-MAY-2013)
i7z DEBUG: Found Intel Processor
i7z DEBUG:    Stepping 4
i7z DEBUG:    Model a
i7z DEBUG:    Family 6
i7z DEBUG:    Processor Type 0
i7z DEBUG:    Extended Model 1
i7z DEBUG: msr = Model Specific Register
i7z DEBUG: Detected a nehalem (i7) - 45nm
i7z DEBUG: msr device files exist /dev/cpu/*/msr
i7z DEBUG: You have write permissions to msr device files

------------------------------
--[core id]--- Other information
-------------------------------------
--[0] Processor number 0
--[0] Socket number/Hyperthreaded Sibling number  0,4
--[0] Core id number 0
--[0] Display core in i7z Tool: Yes

--[1] Processor number 1
--[1] Socket number/Hyperthreaded Sibling number  0,5
--[1] Core id number 1
--[1] Display core in i7z Tool: Yes

--[2] Processor number 2
--[2] Socket number/Hyperthreaded Sibling number  0,6
--[2] Core id number 2
--[2] Display core in i7z Tool: Yes

--[3] Processor number 3
--[3] Socket number/Hyperthreaded Sibling number  0,7
--[3] Core id number 3
--[3] Display core in i7z Tool: Yes

--[4] Processor number 4
--[4] Socket number/Hyperthreaded Sibling number  0,0
--[4] Core id number 0
--[4] Display core in i7z Tool: No

--[5] Processor number 5
--[5] Socket number/Hyperthreaded Sibling number  0,1
--[5] Core id number 1
--[5] Display core in i7z Tool: No

--[6] Processor number 6
--[6] Socket number/Hyperthreaded Sibling number  0,2
--[6] Core id number 2
--[6] Display core in i7z Tool: No

--[7] Processor number 7
--[7] Socket number/Hyperthreaded Sibling number  0,3
--[7] Core id number 3
--[7] Display core in i7z Tool: No

Socket-0 [num of cpus 4 physical 4 logical 8] 0,1,2,3,
Socket-1 [num of cpus 0 physical 0 logical 0] 
GUI has been Turned ON
i7z DEBUG: Single Socket Detected
i7z DEBUG: In i7z Single_Socket()
i7z DEBUG: guessing Haswell
$ 
@James-E-A
Copy link
Author

James-E-A commented Jan 2, 2017

The i7z_rw_registers tool correctly determines the architecture, however:

$ sudo ruby i7z_rw_registers.rb


This script is totally experimental 
use it in superuser mode to get access to r/w access 
also i need msr-tools installed so that rdmsr and wrmsr can work in sudo
write quit or ctrl+C to exit

Now for the blurb on why you might find this script useful:
Throttling cpu on battery is one place, some machines including W520
have a wierd bios which switches off turbo when machine is booted in
battery or some bios implement throttling even when the power is within limit
and this tool should allow you to manually set the multiplier
Whenever you run a command it will print out what goes in the background
like what registers were read/written etc, this should allow one to even
write different scripts to automatically run specifics multiplier in battery
power and other modes.
msr-tools are needed. Furthermore "modprobe msr" on command line needs to be executed
Do you need help? 
Possible commands are 
help : which will print this list again 
turbo : which examines the turbo status 
multiplier : examines the multipliers 
power : which prints current wattage of the system
clock : allows for software clock modulation ( a form of throttling )
system : allows to print some system info
quit : which will quit the program or just do ctrl + c
>> system
number of cores 4
trying to distinguish between nehalem/sandy bridge via AVX support... Nehalem
>> quit
exiting, thanks for using
$ 

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant