1. 30 Nov, 2012 4 commits
    • Mark Asselstine's avatar
      tools/power: turbostat: make Makefile a bit more capable · ee0778a3
      Mark Asselstine authored
      The turbostat Makefile is pretty simple, its output is placed in the
      same directory as the source, the install rule has no concept of a
      prefix or sysroot, and you can set CC to use a specific compiler but
      not use the more familiar CROSS_COMPILE. By making a few minor changes
      these limitations are removed while leaving the default behavior
      matching what it used to be.
      
      Example build with these changes:
      make CROSS_COMPILE=i686-wrs-linux-gnu- DESTDIR=/tmp install
      
      or from the tools directory
      make CROSS_COMPILE=i686-wrs-linux-gnu- DESTDIR=/tmp turbostat_install
      Signed-off-by: default avatarMark Asselstine <mark.asselstine@windriver.com>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      ee0778a3
    • Colin Ian King's avatar
      tools/power x86_energy_perf_policy: close /proc/stat in for_every_cpu() · 84764a41
      Colin Ian King authored
      Instead of returning out of for_every_cpu() we should break out of the loop=
       which will then tidy up correctly by closing the file /proc/stat.
      Signed-off-by: default avatarColin Ian King <colin.king@canonical.com>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      84764a41
    • Len Brown's avatar
      tools/power turbostat: v3.0: monitor Watts and Temperature · 889facbe
      Len Brown authored
      Show power in Watts and temperature in Celsius
      when hardware support is present.
      
      Intel's Sandy Bridge and Ivy Bridge processor generations support RAPL
      (Run-Time-Average-Power-Limiting).  Per the Intel SDM
      (Intel® 64 and IA-32 Architectures Software Developer Manual)
      RAPL provides hardware energy counters and power control MSRs
      (Model Specific Registers).  RAPL MSRs are designed primarily
      as a method to implement power capping.  However, they are useful
      for monitoring system power whether or not power capping is used.
      
      In addition, Turbostat now shows temperature from DTS
      (Digital Thermal Sensor) and PTM (Package Thermal Monitor) hardware,
      if present.
      
      As before, turbostat reads MSRs, and never writes MSRs.
      
      New columns are present in turbostat output:
      
      The Pkg_W column shows Watts for each package (socket) in the system.
      On multi-socket systems, the system summary on the 1st row shows the sum
      for all sockets together.
      
      The Cor_W column shows Watts due to processors cores.
      Note that Core_W is included in Pkg_W.
      
      The optional GFX_W column shows Watts due to the graphics "un-core".
      Note that GFX_W is included in Pkg_W.
      
      The optional RAM_W column on server processors shows Watts due to DRAM DIMMS.
      As DRAM DIMMs are outside the processor package, RAM_W is not included in Pkg_W.
      
      The optional PKG_% and RAM_% columns on server processors shows the % of time
      in the measurement interval that RAPL power limiting is in effect on the
      package and on DRAM.
      
      Note that the RAPL energy counters have some limitations.
      
      First, hardware updates the counters about once every milli-second.
      This is fine for typical turbostat measurement intervals > 1 sec.
      However, when turbostat is used to measure events that approach
      1ms, the counters are less useful.
      
      Second, the 32-bit energy counters are subject to wrapping.
      For example, a counter incrementing 15 micro-Joule units
      on a 130 Watt TDP server processor could (in theory)
      roll over in about 9 minutes.  Turbostat detects and handles
      up to 1 counter overflow per measurement interval.
      But when the measurement interval exceeds the guaranteed
      counter range, we can't detect if more than 1 overflow occured.
      So in this case turbostat indicates that the results are
      in question by replacing the fractional part of the Watts
      in the output with "**":
      
      Pkg_W  Cor_W GFX_W
        3**    0**   0**
      
      Third, the RAPL counters are energy (Joule) counters -- they sum up
      weighted events in the package to estimate energy consumed.  They are
      not analong power (Watt) meters.  In practice, they tend to under-count
      because they don't cover every possible use of energy in the package.
      The accuracy of the RAPL counters will vary between product generations,
      and between SKU's in the same product generation, and with temperature.
      
      turbostat's -v (verbose) option now displays more power and thermal configuration
      information -- as shown on the turbostat.8 manual page.
      For example, it now displays the Package and DRAM Thermal Design Power (TDP):
      
      cpu0: MSR_PKG_POWER_INFO: 0x2f064001980410 (130 W TDP, RAPL 51 - 200 W, 0.045898 sec.)
      cpu0: MSR_DRAM_POWER_INFO,: 0x28025800780118 (35 W TDP, RAPL 15 - 75 W, 0.039062 sec.)
      cpu8: MSR_PKG_POWER_INFO: 0x2f064001980410 (130 W TDP, RAPL 51 - 200 W, 0.045898 sec.)
      cpu8: MSR_DRAM_POWER_INFO,: 0x28025800780118 (35 W TDP, RAPL 15 - 75 W, 0.039062 sec.)
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      889facbe
    • Len Brown's avatar
      tools/power turbostat: fix output buffering issue · ddac0d68
      Len Brown authored
      In periodic mode, turbostat writes to stdout,
      but users were un-able to re-direct stdout, eg.
      
      turbostat > outputfile
      
      would result in an empty outputfile.
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      ddac0d68
  2. 27 Nov, 2012 1 commit
    • Len Brown's avatar
      tools/power turbostat: prevent infinite loop on migration error path · e52966c0
      Len Brown authored
      Turbostat assumed if it can't migrate to a CPU, then the CPU
      must have gone off-line and turbostat should re-initialize
      with the new topology.
      
      But if turbostat can not migrate because it is restricted by
      a cpuset, then it will fail to migrate even after re-initialization,
      resulting in an infinite loop.
      
      Spit out a warning when we can't migrate
      and endure only 2 re-initialize cycles in a row
      before giving up and exiting.
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      e52966c0
  3. 24 Nov, 2012 2 commits
  4. 01 Nov, 2012 2 commits
  5. 30 Oct, 2012 17 commits
  6. 29 Oct, 2012 3 commits
  7. 28 Oct, 2012 11 commits