perf-kmem(1) ============ NAME ---- perf-kmem - Tool to trace/measure kernel memory properties SYNOPSIS -------- [verse] 'perf kmem' {record|stat} [] DESCRIPTION ----------- There are two variants of perf kmem: 'perf kmem record ' to record the kmem events of an arbitrary workload. 'perf kmem stat' to report kernel memory statistics. OPTIONS ------- -i :: --input=:: Select the input file (default: perf.data unless stdin is a fifo) -v:: --verbose:: Be more verbose. (show symbol address, etc) --caller:: Show per-callsite statistics --alloc:: Show per-allocation statistics -s :: --sort=:: Sort the output (default: 'frag,hit,bytes' for slab and 'bytes,hit' for page). Available sort keys are 'ptr, callsite, bytes, hit, pingpong, frag' for slab and 'page, callsite, bytes, hit, order, migtype, gfp' for page. This option should be preceded by one of the mode selection options - i.e. --slab, --page, --alloc and/or --caller. -l :: --line=:: Print n lines only --raw-ip:: Print raw ip instead of symbol --slab:: Analyze SLAB allocator events. --page:: Analyze page allocator events --live:: Show live page stat. The perf kmem shows total allocation stat by default, but this option shows live (currently allocated) pages instead. (This option works with --page option only) --time:: Only analyze samples within given time window: ,. Times have the format seconds.microseconds. If start is not given (i.e., time string is ',x.y') then analysis starts at the beginning of the file. If stop time is not given (i.e, time string is 'x.y,') then analysis goes to end of file. SEE ALSO -------- linkperf:perf-record[1] /arm_arch_timer.h'>logtreecommitdiff
diff options
context:
space:
mode:
authorSrinivas Pandruvada <srinivas.pandruvada@linux.intel.com>2017-02-03 14:18:39 -0800
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2017-02-04 00:11:08 +0100
commit6e978b22efa1db9f6e71b24440b5f1d93e968ee3 (patch)
treec666f7a26b860674848949e39a610222b0723f89 /include/clocksource/arm_arch_timer.h
parent3c223c19aea85d3dda1416c187915f4a30b04b1f (diff)
cpufreq: intel_pstate: Disable energy efficiency optimization
Some Kabylake desktop processors may not reach max turbo when running in HWP mode, even if running under sustained 100% utilization. This occurs when the HWP.EPP (Energy Performance Preference) is set to "balance_power" (0x80) -- the default on most systems. It occurs because the platform BIOS may erroneously enable an energy-efficiency setting -- MSR_IA32_POWER_CTL BIT-EE, which is not recommended to be enabled on this SKU. On the failing systems, this BIOS issue was not discovered when the desktop motherboard was tested with Windows, because the BIOS also neglects to provide the ACPI/CPPC table, that Windows requires to enable HWP, and so Windows runs in legacy P-state mode, where this setting has no effect. Linux' intel_pstate driver does not require ACPI/CPPC to enable HWP, and so it runs in HWP mode, exposing this incorrect BIOS configuration. There are several ways to address this problem. First, Linux can also run in legacy P-state mode on this system. As intel_pstate is how Linux enables HWP, booting with "intel_pstate=disable" will run in acpi-cpufreq/ondemand legacy p-state mode. Or second, the "performance" governor can be used with intel_pstate, which will modify HWP.EPP to 0. Or third, starting in 4.10, the /sys/devices/system/cpu/cpufreq/policy*/energy_performance_preference attribute in can be updated from "balance_power" to "performance". Or fourth, apply this patch, which fixes the erroneous setting of MSR_IA32_POWER_CTL BIT_EE on this model, allowing the default configuration to function as designed. Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> Reviewed-by: Len Brown <len.brown@intel.com> Cc: 4.6+ <stable@vger.kernel.org> # 4.6+ Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'include/clocksource/arm_arch_timer.h')