| /linux/drivers/acpi/ |
| H A D | processor_perflib.c | 79 ppc >= pr->performance->state_count) in acpi_processor_get_platform_limit()
97 qos_value = pr->performance->states[index].core_frequency * 1000; in acpi_processor_get_platform_limit()
127 if (ignore_ppc || !pr->performance) { in acpi_processor_ppc_has_changed()
157 if (!pr || !pr->performance || !pr->performance->state_count) in acpi_processor_get_bios_limit()
160 *limit = pr->performance->states[pr->performance_platform_limit]. in acpi_processor_get_bios_limit()
200 if (!pr->performance) in acpi_processor_ppc_init()
259 memcpy(&pr->performance->control_register, obj.buffer.pointer, in acpi_processor_get_performance_control()
275 memcpy(&pr->performance->status_register, obj.buffer.pointer, in acpi_processor_get_performance_control()
342 pr->performance->state_count = pss->package.count; in acpi_processor_get_performance_states()
343 pr->performance->states = in acpi_processor_get_performance_states()
[all …]
|
| /linux/Documentation/admin-guide/acpi/ |
| H A D | cppc_sysfs.rst | 13 performance of a logical processor on a contiguous and abstract performance
14 scale. CPPC exposes a set of registers to describe abstract performance scale,
15 to request performance levels and to measure per-cpu delivered performance.
40 * highest_perf : Highest performance of this processor (abstract scale).
41 * nominal_perf : Highest sustained performance of this processor
43 * lowest_nonlinear_perf : Lowest performance of this processor with nonlinear
45 * lowest_perf : Lowest performance of this processor (abstract scale).
49 The above frequencies should only be used to report processor performance in
53 * feedback_ctrs : Includes both Reference and delivered performance counter.
54 Reference counter ticks up proportional to processor's reference performance.
[all …]
|
| H A D | fan_performance_states.rst | 10 These attributes list properties of fan performance states.
37 where each of the "state*" files represents one performance state of the fan
47 to this performance state (0-9).
71 Here use can look at fan performance states for a reference speed (speed_rpm)
74 not defined in the performance states.
80 This sysfs attribute is presented in the same directory as performance states.
90 in the same directory as performance states.
|
| /linux/Documentation/admin-guide/pm/ |
| H A D | amd-pstate.rst | 16 ``amd-pstate`` is the AMD CPU performance scaling driver that introduces a
24 communicate the performance hints to hardware.
27 ``ondemand``, etc. to manage the performance hints which are provided by
40 continuous, abstract, and unit-less performance value in a scale that is
41 not tied to a specific performance state / frequency. This is an ACPI
42 standard [2]_ which software can specify application performance goals and
45 interpreter for performance adjustments. ``amd-pstate`` will initialize a
47 to manage each performance update behavior. ::
94 This is the absolute maximum performance an individual processor may reach,
95 assuming ideal conditions. This performance level may not be sustainable
[all …]
|
| H A D | intel-speed-select.rst | 8 collection of features that give more granular control over CPU performance.
9 With Intel(R) SST, one server can be configured for power and performance for a
15 …tel.com/docs/networkbuilders/intel-speed-select-technology-base-frequency-enhancing-performance.pdf
25 how these commands change the power and performance profile of the system under
83 performance requirements. This helps users during deployment as they do not have
86 that allows multiple optimized performance profiles per system. Each profile
89 performance profile and meet CPU online/offline requirement, the user can expect
93 Number or performance levels
96 There can be multiple performance profiles on a system. To get the number of
111 On this system under test, there are 4 performance profiles in addition to the
[all …]
|
| /linux/arch/x86/events/ |
| H A D | Kconfig | 5 tristate "Intel uncore performance events"
9 Include support for Intel uncore performance events. These are
13 tristate "Intel/AMD rapl performance events"
17 Include support for Intel and AMD rapl performance events for power
21 tristate "Intel cstate performance events"
25 Include support for Intel cstate performance events for power
38 tristate "AMD Uncore performance events"
42 Include support for AMD uncore performance events for use with
|
| /linux/Documentation/driver-api/mmc/ |
| H A D | mmc-test.rst | 10 The `mmc_test` framework is designed to test the performance and reliability of host controller dri…
12 …of the host controller and device interactions, such as read and write performance, data integrity…
16 - Verifying the functionality and performance of MMC and SD host controller drivers.
204 | 23 | Best-case read performance | Performs 512K sequential read (non sg) |
206 | 24 | Best-case write performance | same for write |
208 | 25 | Best-case read performance | Same using sg |
211 | 26 | Best-case write performance | same for write |
214 | 27 | Single read performance | By transfer size |
216 | 28 | Single write performance | By transfer size |
218 | 29 | Single trim performance | By transfer size |
[all …]
|
| /linux/Documentation/admin-guide/ |
| H A D | perf-security.rst | 14 depends on the nature of data that perf_events performance monitoring
15 units (PMU) [2]_ and Perf collect and expose for performance analysis.
16 Collected system and performance data may be split into several
21 its topology, used kernel and Perf versions, performance monitoring
30 faults, CPU migrations), architectural hardware performance counters
46 So, perf_events performance monitoring and observability operations are
56 all kernel security permission checks so perf_events performance
70 as privileged processes with respect to perf_events performance
73 privilege [13]_ (POSIX 1003.1e: 2.2.2.39) for performance monitoring and
75 performance monitoring and observability in the system.
[all …]
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-platform-profile | 21 and performance
22 balanced-performance Balance between performance and low
24 towards performance
25 performance High performance operation
26 max-power Higher performance operation that may exceed
|
| H A D | sysfs-platform_profile | 13 and performance
14 balanced-performance Balance between performance and low
16 towards performance
17 performance High performance operation
|
| /linux/Documentation/arch/x86/ |
| H A D | amd-hfi.rst | 17 power capabilities: performance-oriented *classic cores* and power-efficient
27 threads to the classic cores. From a performance perspective, sending
32 performance impact.
37 The ``amd_hfi`` driver delivers the operating system a performance and energy
45 describes an efficiency and performance ranking for each classification.
48 represent thread performance/power characteristics that may benefit from
74 about the performance and energy efficiency of each CPU in the system. Each
76 performance value indicates higher performance capability, and a higher
77 efficiency value indicates more efficiency. Energy efficiency and performance
83 a reordering of the performance and efficiency ranking. Table updates happen
[all …]
|
| H A D | intel-hfi.rst | 14 The HFI gives the operating system a performance and energy efficiency
22 about the performance and energy efficiency of each CPU in the system. Each
24 indicate higher capability. Energy efficiency and performance are reported in
35 excessive heat, the HFI may reflect reduced performance on specific CPUs.
38 task placement decisions. For instance, if either the performance or energy
41 that processor for performance or energy efficiency reasons, respectively.
|
| /linux/drivers/perf/hisilicon/ |
| H A D | Kconfig | 6 Support for HiSilicon SoC L3 Cache performance monitor, Hydra Home
7 Agent performance monitor and DDR Controller performance monitor.
13 Provide support for HiSilicon PCIe performance monitoring unit (PMU)
23 Provide support for HNS3 performance monitoring unit (PMU) RCiEP
|
| /linux/Documentation/admin-guide/perf/ |
| H A D | hns3-pmu.rst | 6 End Point device to collect performance statistics of HiSilicon SoC NIC.
9 HNS3 PMU supports collection of performance statistics such as bandwidth,
48 Each performance statistic has a pair of events to get two values to
49 calculate real performance data in userspace.
57 computation to calculate real performance data is:::
82 PMU collect performance statistics for all HNS3 PCIe functions of IO DIE.
89 PMU collect performance statistic of one whole physical port. The port id
98 PMU collect performance statistic of one tc of physical port. The port id
106 PMU collect performance statistic of one PF/VF. The function id is BDF of
123 PMU collect performance statistic of one queue of PF/VF. The function id
[all …]
|
| /linux/Documentation/scheduler/ |
| H A D | sched-util-clamp.rst | 11 feature that allows user space to help in managing the performance requirement
16 performance requirements and restrictions of the tasks, thus it helps the
23 system run at a certain performance point.
26 performance constraints. It consists of two tunables:
31 These two bounds will ensure a task will operate within this performance range
36 performance point to operate at to deliver the desired user experience. Or one
38 much resources and should not go above a specific performance point. Viewing
39 the uclamp values as performance points rather than utilization is a better
44 performance point required by its display pipeline to ensure no frame is
58 resources background tasks are consuming by capping the performance point they
[all …]
|
| /linux/drivers/xen/ |
| H A D | xen-acpi-processor.c | 145 _pr->performance->state_count); in xen_copy_pss_data()
149 dst_perf->state_count = _pr->performance->state_count; in xen_copy_pss_data()
150 for (i = 0; i < _pr->performance->state_count; i++) { in xen_copy_pss_data()
152 memcpy(&(dst_states[i]), &(_pr->performance->states[i]), in xen_copy_pss_data()
168 dst->shared_type = _pr->performance->shared_type; in xen_copy_psd_data()
170 pdomain = &(_pr->performance->domain_info); in xen_copy_psd_data()
219 xen_copy_pct_data(&(_pr->performance->control_register), in push_pxx_to_hypervisor()
221 xen_copy_pct_data(&(_pr->performance->status_register), in push_pxx_to_hypervisor()
246 perf = _pr->performance; in push_pxx_to_hypervisor()
279 if (_pr->performance && _pr->performance->states) in upload_pm_data()
[all …]
|
| /linux/tools/power/cpupower/bench/ |
| H A D | README-BENCH | 7 - Identify worst case performance loss when doing dynamic frequency
12 - Identify cpufreq related performance regressions between kernels
18 - Power saving related regressions (In fact as better the performance
28 For that purpose, it compares the performance governor to a configured
56 takes on this machine and needs to be run in a loop using the performance
58 Then the above test runs are processed using the performance governor
61 on full performance and you get the overall performance loss.
80 trigger of the cpufreq-bench, you will see no performance loss (compare with
84 will always see 50% loads and you get worst performance impact never
|
| /linux/drivers/perf/ |
| H A D | Kconfig | 63 Say y if you want to use CPU performance monitors on ARM-based
83 Say y if you want to use CPU performance monitors on RISCV-based
93 Say y if you want to use the legacy CPU performance monitor
103 Say y if you want to use the CPU performance monitor
151 Say y if you want to use the ARM performance monitor unit (PMU)
152 version 3. The PMUv3 is the CPU performance monitors on ARMv8
160 Provides support for performance monitor unit in ARM DynamIQ Shared
169 Provides support for the DDR performance monitor in i.MX8, which
177 Provides support for the DDR performance monitor in i.MX9, which
185 Provides support for the Uncore performance monitor unit (PMU)
[all …]
|
| /linux/arch/arm64/boot/dts/apple/ |
| H A D | t6022.dtsi | 86 performance-domains = <&cpufreq_e_die1>;
100 performance-domains = <&cpufreq_e_die1>;
114 performance-domains = <&cpufreq_e_die1>;
128 performance-domains = <&cpufreq_e_die1>;
142 performance-domains = <&cpufreq_p0_die1>;
156 performance-domains = <&cpufreq_p0_die1>;
170 performance-domains = <&cpufreq_p0_die1>;
184 performance-domains = <&cpufreq_p0_die1>;
198 performance-domains = <&cpufreq_p1_die1>;
212 performance-domains = <&cpufreq_p1_die1>;
[all …]
|
| H A D | t6002.dtsi | 80 performance-domains = <&cpufreq_e_die1>;
94 performance-domains = <&cpufreq_e_die1>;
108 performance-domains = <&cpufreq_p0_die1>;
122 performance-domains = <&cpufreq_p0_die1>;
136 performance-domains = <&cpufreq_p0_die1>;
150 performance-domains = <&cpufreq_p0_die1>;
164 performance-domains = <&cpufreq_p1_die1>;
178 performance-domains = <&cpufreq_p1_die1>;
192 performance-domains = <&cpufreq_p1_die1>;
206 performance-domains = <&cpufreq_p1_die1>;
|
| H A D | t602x-common.dtsi | 80 performance-domains = <&cpufreq_e>;
94 performance-domains = <&cpufreq_e>;
108 performance-domains = <&cpufreq_e>;
122 performance-domains = <&cpufreq_e>;
136 performance-domains = <&cpufreq_p0>;
150 performance-domains = <&cpufreq_p0>;
164 performance-domains = <&cpufreq_p0>;
178 performance-domains = <&cpufreq_p0>;
192 performance-domains = <&cpufreq_p1>;
206 performance-domains = <&cpufreq_p1>;
[all …]
|
| H A D | t600x-common.dtsi | 74 performance-domains = <&cpufreq_e>;
88 performance-domains = <&cpufreq_e>;
102 performance-domains = <&cpufreq_p0>;
116 performance-domains = <&cpufreq_p0>;
130 performance-domains = <&cpufreq_p0>;
144 performance-domains = <&cpufreq_p0>;
158 performance-domains = <&cpufreq_p1>;
172 performance-domains = <&cpufreq_p1>;
186 performance-domains = <&cpufreq_p1>;
200 performance-domains = <&cpufreq_p1>;
|
| /linux/Documentation/power/ |
| H A D | energy-model.rst | 11 the power consumed by devices at various performance levels, and the kernel
68 'performance domain' in the system. A performance domain is a group of CPUs
69 whose performance is scaled together. Performance domains generally have a
70 1-to-1 mapping with CPUFreq policies. All CPUs in a performance domain are
71 required to have the same micro-architecture. CPUs in different performance
94 It is possible also to modify the CPU performance values for each EM's
95 performance state. Thus, the full power and performance profile (which
109 2.2 Registration of performance domains
118 the real power measurements performed for each performance state. Thus, this
122 Drivers are expected to register performance domains into the EM framework by
[all …]
|
| /linux/Documentation/userspace-api/ |
| H A D | sysfs-platform_profile.rst | 5 On modern systems the platform performance, temperature, fan and other
13 operation or towards performance.
19 NOT a goal of this API to allow monitoring the resulting performance
20 characteristics. Monitoring performance is best done with device/vendor
23 Specifically, when selecting a high performance profile the actual achieved
24 performance may be limited by various factors such as: the heat generated
28 performance level.
|
| /linux/drivers/pmdomain/qcom/ |
| H A D | Kconfig | 25 performance states. The driver communicates a performance state
37 performance states. The driver communicates a performance state
|