Hosts the 0x221E linux distro kernel. https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.7.y 2012-11-01T04:22:00Z 2012-11-01T04:22:00Z Len Brown 2012-11-01T04:08:19Z urn:sha1:d91bb17c2a874493603c4d99db305d8caf2d180c When invald MSR's are specified on the command line, turbostat should simply print an error and exit. Signed-off-by: Len Brown <len.brown@intel.com> 2012-11-01T04:21:43Z Len Brown 2012-11-01T04:16:34Z urn:sha1:39300ffb9b6666714c60735cf854e1280e4e75f4 Fix regression caused by commit 8e180f3cb6b7510a3bdf14e16ce87c9f5d86f102 (tools/power turbostat: add [-d MSR#][-D MSR#] options to print counter deltas) Signed-off-by: Len Brown <len.brown@intel.com> 2012-10-06T19:26:31Z Len Brown 2012-10-06T19:26:31Z urn:sha1:f9240813e61cb3e5838c9ab0237af831c61df7cf Counting SMIs is popular, so add a dedicated "-s" option to do it, and juggle some of the other option letters. -S is now system summary (was -s) -c is 32 bit counter (was -d) -C is 64-bit counter (was -D) -p is 1st thread in core (was -c) -P is 1st thread in package (was -p) bump the minor version number Signed-off-by: Len Brown <len.brown@intel.com> 2012-09-28T02:04:56Z Len Brown 2012-09-22T05:25:08Z urn:sha1:8e180f3cb6b7510a3bdf14e16ce87c9f5d86f102 # turbostat -d 0x34 is useful for printing the number of SMI's within an interval on Nehalem and newer processors. where # turbostat -m 0x34 will simply print out the total SMI count since reset. Suggested-by: Andi Kleen Signed-off-by: Len Brown <len.brown@intel.com> 2012-09-26T22:17:21Z Len Brown 2012-09-22T03:45:46Z urn:sha1:2f32edf12c1eafc8e5b1b0337360993fde1b3565 -m MSR# prints the specified MSR in 32-bit format -M MSR# prints the specified MSR in 64-bit format Signed-off-by: Len Brown <len.brown@intel.com> 2012-09-26T22:17:21Z Len Brown 2012-09-22T02:56:06Z urn:sha1:130ff304f6d31484fc73bb337bc635cba1ffe04c The -M option dumps the specified 64-bit MSR with every sample. Previously it was output at the end of each line. However, with the v2 style of printing, the lines are now staggered, making MSR output hard to read. So move the MSR output column to the left where things are aligned. Signed-off-by: Len Brown <len.brown@intel.com> 2012-09-26T22:15:48Z Len Brown 2012-09-21T04:01:31Z urn:sha1:6574a5d5053cd3b8e7c088900b80a9ff51895450 The "turbo-limit" is the maximum opportunistic processor speed, assuming no electrical or thermal constraints. For a given processor, the turbo-limit varies, depending on the number of active cores. Generally, there is more opportunity when fewer cores are active. Under the "-v" verbose option, turbostat would print the turbo-limits for the four cases of 1 to 4 cores active. Expand that capability to cover the cases of turbo opportunities with up to 16 cores active. Note that not all hardware platforms supply this information, and that sometimes a valid limit may be specified for a core which is not actually present. Signed-off-by: Len Brown <len.brown@intel.com> 2012-09-26T22:11:48Z Len Brown 2012-09-20T17:43:07Z urn:sha1:d7db69016548c4bf3bec3556f6a15b9332dae34f MSR_TSC is no longer needed because we now use RDTSC directly. Signed-off-by: Len Brown <len.brown@intel.com> 2012-09-26T22:11:31Z Len Brown 2012-09-26T22:11:31Z urn:sha1:1300651b40298ce60ee628b8f13f8c121706b06c This fix is required to run on IVB Xeon, which previously had an incorrect cpuid model number listed. Signed-off-by: Len Brown <len.brown@intel.com> 2012-07-20T02:26:33Z Len Brown 2012-06-14T01:31:46Z urn:sha1:c3ae331d1c2fe25edfbece73fda0bb312445b636 Under some conditions, c1% was displayed as very large number, much higher than 100%. c1% is not measured, it is derived as "that, which is left over" from other counters. However, the other counters are not collected atomically, and so it is possible for c1% to be calaculagted as a small negative number -- displayed as very large positive. There was a check for mperf vs tsc for this already, but it needed to also include the other counters that are used to calculate c1. Signed-off-by: Len Brown <len.brown@intel.com>