/linux/Documentation/devicetree/bindings/dvfs/ |
H A D | performance-domain.yaml | 4 $id: http://devicetree.org/schemas/dvfs/performance-domain.yaml# 7 title: Generic performance domains 25 devices with their performance domains provided by performance domain 30 \#performance-domain-cells property in the performance domain provider node. 35 "#performance-domain-cells": 39 multiple performance domains (e.g. performance controllers), but can be 44 performance-domains: 58 performance: performance-controller@11bc00 { 62 #performance-domain-cells = <1>; 66 // The node above defines a performance controller that is a performance [all …]
|
/linux/drivers/acpi/ |
H A D | processor_perflib.c | 158 if (!pr || !pr->performance || !pr->performance->state_count) in acpi_processor_get_bios_limit() 333 pr->performance->states = in acpi_processor_get_performance_states() 613 if (pr->performance) { in acpi_processor_preregister_performance() 618 if (!performance || !per_cpu_ptr(performance, i)) { in acpi_processor_preregister_performance() 630 pr->performance = per_cpu_ptr(performance, i); in acpi_processor_preregister_performance() 752 if (pr->performance) { in acpi_processor_register_performance() 757 WARN_ON(!performance); in acpi_processor_register_performance() 759 pr->performance = performance; in acpi_processor_register_performance() 762 pr->performance = NULL; in acpi_processor_register_performance() 782 if (pr->performance) in acpi_processor_unregister_performance() [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. 58 * reference_perf : Performance level at which reference performance counter [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/devicetree/bindings/cpufreq/ |
H A D | cpufreq-mediatek-hw.yaml | 29 "#performance-domain-cells": 31 Number of cells in a performance domain specifier. 33 performance domains. 39 - "#performance-domain-cells" 53 performance-domains = <&performance 0>; 64 performance: performance-controller@11bc00 { 68 #performance-domain-cells = <1>;
|
H A D | apple,cluster-cpufreq.yaml | 15 operating-points-v2 table to define the CPU performance states, with the 34 '#performance-domain-cells': 40 - '#performance-domain-cells' 58 performance-domains = <&cpufreq_e>; 66 performance-domains = <&cpufreq_p>; 106 cpufreq_e: performance-controller@210e20000 { 109 #performance-domain-cells = <0>; 112 cpufreq_p: performance-controller@211e20000 { 115 #performance-domain-cells = <0>;
|
/linux/Documentation/admin-guide/pm/ |
H A D | amd-pstate.rst | 24 communicate the performance hints to hardware. 123 performance level lower than the lowest nonlinear performance level may 133 Minimum requested performance (RW) 138 Maximum requested performance (RW) 144 Desired performance target (RW) 149 performance (infrastructure max). Below the nominal sustained performance 150 level, desired performance expresses the average performance level of the 341 performance preference registers. 369 performance (infrastructure max). Below the nominal sustained performance level, 370 desired performance expresses the average performance level of the processor subject [all …]
|
H A D | intel-speed-select.rst | 93 Number or performance levels 112 base performance profile (which is performance level 0). 138 Properties of a performance level 164 performance level 0. 193 Get current performance level 238 Changing performance level 569 performance, execute some workload and measure performance and get a baseline 570 performance to compare against. 586 performance using Intel(R) SST-BF. 589 number means better performance:: [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 | 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 | 220 | 30 | Consecutive read performance | By transfer size | 222 | 31 | Consecutive write performance | By transfer size | [all …]
|
/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/ABI/testing/ |
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
|
H A D | sysfs-class-fc_host | 7 performance impact notification (FPIN) event. 15 performance impact notification (FPIN) event. 23 performance impact notification (FPIN) event.
|
H A D | sysfs-class-fc_remote_ports | 7 performance impact notification (FPIN) event. 15 performance impact notification (FPIN) event. 23 performance impact notification (FPIN) event.
|
/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 75 performance monitoring and observability in the system. 233 performance data. This is the least secure mode since allowed [all …]
|
/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/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/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: 95 performance/watt if used effectively. 268 highest performance point. 330 Uclamp performance request has the range of 0 to 1024 inclusive. 346 at when this task is running. Or lower performance bound. 348 at when this task is running. Or upper performance bound. 515 performance point all the time. [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/xen/ |
H A D | xen-acpi-processor.c | 145 dst_states = kcalloc(_pr->performance->state_count, in xen_copy_pss_data() 150 dst_perf->state_count = _pr->performance->state_count; in xen_copy_pss_data() 151 for (i = 0; i < _pr->performance->state_count; i++) { in xen_copy_pss_data() 169 dst->shared_type = _pr->performance->shared_type; in xen_copy_psd_data() 171 pdomain = &(_pr->performance->domain_info); in xen_copy_psd_data() 220 xen_copy_pct_data(&(_pr->performance->control_register), in push_pxx_to_hypervisor() 222 xen_copy_pct_data(&(_pr->performance->status_register), in push_pxx_to_hypervisor() 247 perf = _pr->performance; in push_pxx_to_hypervisor() 280 if (_pr->performance && _pr->performance->states) in upload_pm_data() 437 memcpy(&pr_backup->performance->domain_info, in check_acpi_ids() [all …]
|
/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 169 Provides support for the DDR performance monitor in i.MX8, which 177 Provides support for the DDR performance monitor in i.MX9, which 238 performance monitors on CN10K family silicons. 278 Support performance monitoring as defined in CXL rev 3.0 [all …]
|
/linux/arch/arm64/boot/dts/apple/ |
H A D | t6002.dtsi | 78 performance-domains = <&cpufreq_e_die1>; 92 performance-domains = <&cpufreq_e_die1>; 106 performance-domains = <&cpufreq_p0_die1>; 120 performance-domains = <&cpufreq_p0_die1>; 134 performance-domains = <&cpufreq_p0_die1>; 148 performance-domains = <&cpufreq_p0_die1>; 162 performance-domains = <&cpufreq_p1_die1>; 176 performance-domains = <&cpufreq_p1_die1>; 190 performance-domains = <&cpufreq_p1_die1>; 204 performance-domains = <&cpufreq_p1_die1>;
|
H A D | t600x-common.dtsi | 70 performance-domains = <&cpufreq_e>; 84 performance-domains = <&cpufreq_e>; 98 performance-domains = <&cpufreq_p0>; 112 performance-domains = <&cpufreq_p0>; 126 performance-domains = <&cpufreq_p0>; 140 performance-domains = <&cpufreq_p0>; 154 performance-domains = <&cpufreq_p1>; 168 performance-domains = <&cpufreq_p1>; 182 performance-domains = <&cpufreq_p1>; 196 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 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 155 knowledge about power value for each performance state. The callback 184 2.3 Accessing performance domains 191 performance domain. 195 the performance domains, and kept in memory untouched. 234 performance overhead. [all …]
|
/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
|