Okay. Right away I notice a difference with the program i7z:

Cpu speed from cpuinfo 2875.00Mhz
cpuinfo might be wrong if cpufreq is enabled. To guess correctly try estimating 
via tsc
Linux's inbuilt cpu_khz code emulated now
True Frequency (without accounting Turbo) 2895 MHz
  CPU Multiplier 29x || Bus clock frequency (BCLK) 99.83 MHz

Socket [0] - [physical cores=4, logical cores=8, max online cores ever=4]
  TURBO ENABLED on 4 Cores, Hyper Threading ON
  Max Frequency without considering Turbo 2994.83 MHz (99.83 x [30])
  Max TURBO Multiplier (if Enabled) with 1/2/3/4 Cores is  39x/37x/36x/35x
  Real Current Frequency 2881.62 MHz [99.83 x 28.87] (Max of below)
        Core [core-id]  :Actual Freq (Mult.)      C0%   Halt(C1)%  C3 %   C6 %  
Temp      VCore
        Core 1 [0]:       2865.41 (28.70x)      1.77    96.2       1       1    
46      1.0009
        Core 2 [1]:       2874.93 (28.80x)      1.74    86.3       1      11    
46      0.9927
        Core 3 [2]:       2881.62 (28.87x)      1.34    96.1       1    1.55    
46      1.0076
        Core 4 [3]:       2877.37 (28.82x)       1.4      95       1    2.62    
46      1.0226


C0 = Processor running without halting
C1 = Processor running with halts (States >C0 are power saver modes with cores 
idling)
C3 = Cores running with PLL turned off and core cache turned off
C6, C7 = Everything in C3 + core state saved to last level cache, C7 is deeper 
than C6
  Above values in table are in percentage over the last 1 sec


WAY MORE activity in C6 state. Although I don't see any listings for C10

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672439

Title:
  No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision
  5520

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672439/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to