diff options
Diffstat (limited to 'Documentation/ABI/testing/sysfs-devices-system-cpu')
| -rw-r--r-- | Documentation/ABI/testing/sysfs-devices-system-cpu | 137 | 
1 files changed, 80 insertions, 57 deletions
diff --git a/Documentation/ABI/testing/sysfs-devices-system-cpu b/Documentation/ABI/testing/sysfs-devices-system-cpu index 7564e88bfa4..acb9bfc89b4 100644 --- a/Documentation/ABI/testing/sysfs-devices-system-cpu +++ b/Documentation/ABI/testing/sysfs-devices-system-cpu @@ -9,31 +9,6 @@ Description:  		/sys/devices/system/cpu/cpu#/ -What:		/sys/devices/system/cpu/sched_mc_power_savings -		/sys/devices/system/cpu/sched_smt_power_savings -Date:		June 2006 -Contact:	Linux kernel mailing list <linux-kernel@vger.kernel.org> -Description:	Discover and adjust the kernel's multi-core scheduler support. - -		Possible values are: - -		0 - No power saving load balance (default value) -		1 - Fill one thread/core/package first for long running threads -		2 - Also bias task wakeups to semi-idle cpu package for power -		    savings - -		sched_mc_power_savings is dependent upon SCHED_MC, which is -		itself architecture dependent. - -		sched_smt_power_savings is dependent upon SCHED_SMT, which -		is itself architecture dependent. - -		The two files are independent of each other. It is possible -		that one file may be present without the other. - -		Introduced by git commit 5c45bf27. - -  What:		/sys/devices/system/cpu/kernel_max  		/sys/devices/system/cpu/offline  		/sys/devices/system/cpu/online @@ -92,20 +67,6 @@ Description:	Discover NUMA node a CPU belongs to  		/sys/devices/system/cpu/cpu42/node2 -> ../../node/node2 -What:		/sys/devices/system/cpu/cpu#/node -Date:		October 2009 -Contact:	Linux memory management mailing list <linux-mm@kvack.org> -Description:	Discover NUMA node a CPU belongs to - -		When CONFIG_NUMA is enabled, a symbolic link that points -		to the corresponding NUMA node directory. - -		For example, the following symlink is created for cpu42 -		in NUMA node 2: - -		/sys/devices/system/cpu/cpu42/node2 -> ../../node/node2 - -  What:		/sys/devices/system/cpu/cpu#/topology/core_id  		/sys/devices/system/cpu/cpu#/topology/core_siblings  		/sys/devices/system/cpu/cpu#/topology/core_siblings_list @@ -167,7 +128,7 @@ Description:	Discover cpuidle policy and mechanism  What:		/sys/devices/system/cpu/cpu#/cpufreq/*  Date:		pre-git history -Contact:	cpufreq@vger.kernel.org +Contact:	linux-pm@vger.kernel.org  Description:	Discover and change clock speed of CPUs  		Clock scaling allows you to change the clock speed of the @@ -183,21 +144,83 @@ Description:	Discover and change clock speed of CPUs  		to learn how to control the knobs. -What:      /sys/devices/system/cpu/cpu*/cache/index*/cache_disable_X -Date:      August 2008 +What:		/sys/devices/system/cpu/cpu#/cpufreq/freqdomain_cpus +Date:		June 2013 +Contact:	linux-pm@vger.kernel.org +Description:	Discover CPUs in the same CPU frequency coordination domain + +		freqdomain_cpus is the list of CPUs (online+offline) that share +		the same clock/freq domain (possibly at the hardware level). +		That information may be hidden from the cpufreq core and the +		value of related_cpus may be different from freqdomain_cpus. This +		attribute is useful for user space DVFS controllers to get better +		power/performance results for platforms using acpi-cpufreq. + +		This file is only present if the acpi-cpufreq driver is in use. + + +What:		/sys/devices/system/cpu/cpu*/cache/index3/cache_disable_{0,1} +Date:		August 2008  KernelVersion:	2.6.27 -Contact:	mark.langsdorf@amd.com -Description:	These files exist in every cpu's cache index directories. -		There are currently 2 cache_disable_# files in each -		directory.  Reading from these files on a supported -		processor will return that cache disable index value -		for that processor and node.  Writing to one of these -		files will cause the specificed cache index to be disabled. - -		Currently, only AMD Family 10h Processors support cache index -		disable, and only for their L3 caches.  See the BIOS and -		Kernel Developer's Guide at -		http://support.amd.com/us/Embedded_TechDocs/31116-Public-GH-BKDG_3-28_5-28-09.pdf	 -		for formatting information and other details on the -		cache index disable. -Users:    joachim.deguara@amd.com +Contact:	discuss@x86-64.org +Description:	Disable L3 cache indices + +		These files exist in every CPU's cache/index3 directory. Each +		cache_disable_{0,1} file corresponds to one disable slot which +		can be used to disable a cache index. Reading from these files +		on a processor with this functionality will return the currently +		disabled index for that node. There is one L3 structure per +		node, or per internal node on MCM machines. Writing a valid +		index to one of these files will cause the specificed cache +		index to be disabled. + +		All AMD processors with L3 caches provide this functionality. +		For details, see BKDGs at +		http://developer.amd.com/documentation/guides/Pages/default.aspx + + +What:		/sys/devices/system/cpu/cpufreq/boost +Date:		August 2012 +Contact:	Linux kernel mailing list <linux-kernel@vger.kernel.org> +Description:	Processor frequency boosting control + +		This switch controls the boost setting for the whole system. +		Boosting allows the CPU and the firmware to run at a frequency +		beyound it's nominal limit. +		More details can be found in Documentation/cpu-freq/boost.txt + + +What:		/sys/devices/system/cpu/cpu#/crash_notes +		/sys/devices/system/cpu/cpu#/crash_notes_size +Date:		April 2013 +Contact:	kexec@lists.infradead.org +Description:	address and size of the percpu note. + +		crash_notes: the physical address of the memory that holds the +		note of cpu#. + +		crash_notes_size: size of the note of cpu#. + + +What:		/sys/devices/system/cpu/intel_pstate/max_perf_pct +		/sys/devices/system/cpu/intel_pstate/min_perf_pct +		/sys/devices/system/cpu/intel_pstate/no_turbo +Date:		February 2013 +Contact:	linux-pm@vger.kernel.org +Description:	Parameters for the Intel P-state driver + +		Logic for selecting the current P-state in Intel +		Sandybridge+ processors. The three knobs control +		limits for the P-state that will be requested by the +		driver. + +		max_perf_pct: limits the maximum P state that will be requested by +		the driver stated as a percentage of the available performance. + +		min_perf_pct: limits the minimum P state that will be requested by +		the driver stated as a percentage of the available performance. + +		no_turbo: limits the driver to selecting P states below the turbo +		frequency range. + +		More details can be found in Documentation/cpu-freq/intel-pstate.txt  | 
