| /Linux-v6.1/Documentation/devicetree/bindings/dvfs/ |
| D | performance-domain.yaml | 4 $id: http://devicetree.org/schemas/dvfs/performance-domain.yaml#
7 title: Generic performance domains
13 This binding is intended for performance management of groups of devices or
14 CPUs that run in the same performance domain. Performance domains must not
15 be confused with power domains. A performance domain is defined by a set
16 of devices that always have to run at the same performance level. For a given
17 performance domain, there is a single point of control that affects all the
18 devices in the domain, making it impossible to set the performance level of
21 have a common frequency control, is said to be in the same performance
24 This device tree binding can be used to bind performance domain consumer
[all …]
|
| /Linux-v6.1/Documentation/admin-guide/pm/ |
| D | amd-pstate.rst | 5 ``amd-pstate`` CPU Performance Scaling Driver
16 ``amd-pstate`` is the AMD CPU performance scaling driver that introduces a
19 Performance Control (CPPC) which provides finer grain frequency management
24 communicate the performance hints to hardware.
27 ``ondemand``, etc. to manage the performance hints which are provided by
39 Collaborative Processor Performance Control (CPPC) interface enumerates a
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
[all …]
|
| 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
79 Intel(R) Speed Select Technology - Performance Profile (Intel(R) SST-PP)
83 performance requirements. This helps users during deployment as they do not have
85 Technology - Performance Profile (Intel(R) SST-PP) feature introduces a mechanism
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
[all …]
|
| D | intel_pstate.rst | 5 ``intel_pstate`` CPU Performance Scaling Driver
17 :doc:`CPU performance scaling subsystem <cpufreq>` in the Linux kernel
25 than just an operating frequency or an operating performance point (see the
30 uses frequencies for identifying operating performance points of CPUs and
58 active mode, it uses its own internal performance scaling governor algorithm or
59 allows the hardware to do performance scaling by itself, while in the passive
61 a certain performance scaling algorithm. Which of them will be in effect
88 active mode: ``powersave`` and ``performance``. The way they both operate
94 Namely, if that option is set, the ``performance`` algorithm will be used by
117 HWP + ``performance``
[all …]
|
| D | intel_epb.rst | 5 Intel Performance and Energy Bias Hint
16 Intel Performance and Energy Bias Attribute in ``sysfs``
19 The Intel Performance and Energy Bias Hint (EPB) value for a given (logical) CPU
26 a value of 0 corresponds to a hint preference for highest performance
31 with one of the strings: "performance", "balance-performance", "normal",
|
| /Linux-v6.1/drivers/acpi/ |
| D | processor_perflib.c | 25 #define ACPI_PROCESSOR_FILE_PERFORMANCE "performance"
80 if (ppc >= pr->performance->state_count || in acpi_processor_get_platform_limit()
85 pr->performance->states[ppc].core_frequency * 1000); in acpi_processor_get_platform_limit()
99 * 0: success. OSPM is now using the performance state specified.
113 if (ignore_ppc || !pr->performance) { in acpi_processor_ppc_has_changed()
143 if (!pr || !pr->performance || !pr->performance->state_count) in acpi_processor_get_bios_limit()
145 *limit = pr->performance->states[pr->performance_platform_limit]. in acpi_processor_get_bios_limit()
224 memcpy(&pr->performance->control_register, obj.buffer.pointer, in acpi_processor_get_performance_control()
241 memcpy(&pr->performance->status_register, obj.buffer.pointer, in acpi_processor_get_performance_control()
309 acpi_handle_debug(pr->handle, "Found %d performance states\n", in acpi_processor_get_performance_states()
[all …]
|
| /Linux-v6.1/Documentation/admin-guide/acpi/ |
| D | cppc_sysfs.rst | 4 Collaborative Processor Performance Control (CPPC)
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.
[all …]
|
| D | fan_performance_states.rst | 4 ACPI Fan Performance States
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.
82 ACPI Fan Performance Feedback
90 in the same directory as performance states.
|
| /Linux-v6.1/include/linux/ |
| D | energy_model.h | 14 * struct em_perf_state - Performance state of a performance domain
32 * EM_PERF_STATE_INEFFICIENT: The performance state is inefficient. There is
33 * in this em_perf_domain, another performance state with a higher frequency
40 * struct em_perf_domain - Performance domain
41 * @table: List of performance states, in ascending order
42 * @nr_perf_states: Number of performance states
45 * for performance reasons to avoid potential cache
49 * In case of CPU device, a "performance domain" represents a group of CPUs
50 * whose performance is scaled together. All CPUs of a performance domain
51 * must have the same micro-architecture. Performance domains often have
[all …]
|
| D | amd-pstate.h | 20 * @aperf: actual performance frequency clock count
21 * @mperf: maximum performance frequency clock count
34 * @cppc_req_cached: cached performance request hints
35 * @highest_perf: the maximum performance an individual processor may reach,
37 * @nominal_perf: the maximum sustained performance level of the processor,
39 * @lowest_nonlinear_perf: the lowest performance level at which nonlinear power
41 * @lowest_perf: the absolute lowest performance level of the processor
|
| /Linux-v6.1/tools/power/x86/x86_energy_perf_policy/ |
| D | x86_energy_perf_policy.8 | 5 x86_energy_perf_policy \- Manage Energy vs. Performance Policy via x86 Model Specific Registers
18 .RB "value: # | default | performance | balance-performance | balance-power | power"
21 displays and updates energy-performance policy settings specific to
28 and Processor Performance States (P-states).
31 Further, it allows the OS to influence energy/performance trade-offs where there
82 Set a policy with a normal balance between performance and energy efficiency.
83 The processor will tolerate minor performance compromise
88 .I performance
89 Set a policy for maximum performance,
90 accepting no performance sacrifice for the benefit of energy efficiency.
[all …]
|
| /Linux-v6.1/arch/powerpc/include/asm/ |
| D | reg_fsl_emb.h | 3 * Contains register definitions for the Freescale Embedded Performance
13 /* Performance Monitor Registers */
20 /* Freescale Book E Performance Monitor APU Registers */
21 #define PMRN_PMC0 0x010 /* Performance Monitor Counter 0 */
22 #define PMRN_PMC1 0x011 /* Performance Monitor Counter 1 */
23 #define PMRN_PMC2 0x012 /* Performance Monitor Counter 2 */
24 #define PMRN_PMC3 0x013 /* Performance Monitor Counter 3 */
25 #define PMRN_PMC4 0x014 /* Performance Monitor Counter 4 */
26 #define PMRN_PMC5 0x015 /* Performance Monitor Counter 5 */
67 #define PMRN_UPMC0 0x000 /* User Performance Monitor Counter 0 */
[all …]
|
| /Linux-v6.1/Documentation/admin-guide/ |
| D | perf-security.rst | 9 Usage of Performance Counters for Linux (perf_events) [1]_ , [2]_ , [3]_
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
[all …]
|
| /Linux-v6.1/drivers/perf/ |
| D | Kconfig | 3 # Performance Monitor Drivers
6 menu "Performance monitor support"
56 Say y if you want to use CPU performance monitors on ARM-based
64 Say y if you want to use CPU performance monitors on RISCV-based
74 Say y if you want to use the legacy CPU performance monitor
84 Say y if you want to use the CPU performance monitor
94 tristate "ARM SMMUv3 Performance Monitors Extension"
98 Provides support for the ARM SMMUv3 Performance Monitor Counter
107 Provides support for performance monitor unit in ARM DynamIQ Shared
116 Provides support for the DDR performance monitor in i.MX8, which
[all …]
|
| /Linux-v6.1/drivers/gpu/drm/msm/disp/dpu1/ |
| D | dpu_core_perf.h | 31 * struct dpu_core_perf_params - definition of performance parameters
43 * struct dpu_core_perf_tune - definition of performance tuning control
44 * @mode: performance mode
55 * struct dpu_core_perf - definition of core performance context
62 * @perf_tune: debug control for performance tuning
83 * dpu_core_perf_crtc_check - validate performance of the given crtc state
92 * dpu_core_perf_crtc_update - update performance of the given crtc
108 * dpu_core_perf_destroy - destroy the given core performance context
109 * @perf: Pointer to core performance context
114 * dpu_core_perf_init - initialize the given core performance context
[all …]
|
| /Linux-v6.1/arch/x86/events/ |
| D | Kconfig | 2 menu "Performance monitoring"
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-v6.1/Documentation/devicetree/bindings/cpufreq/ |
| 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>;
|
| /Linux-v6.1/Documentation/admin-guide/perf/ |
| D | hns3-pmu.rst | 2 HNS3 Performance Monitoring Unit (PMU)
5 HNS3(HiSilicon network system 3) Performance Monitoring Unit (PMU) is an
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
[all …]
|
| /Linux-v6.1/Documentation/power/ |
| 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
84 2.2 Registration of performance domains
93 the real power measurements performed for each performance state. Thus, this
97 Drivers are expected to register performance domains into the EM framework by
104 for each performance state. The callback function provided by the driver is free
107 performance domains using cpumask. For other devices than CPUs the last
[all …]
|
| /Linux-v6.1/kernel/power/ |
| D | energy_model.c | 21 * Mutex serializing the registrations of performance domains and letting
72 /* Create the directory of the performance domain */ in em_debug_create_pd()
82 /* Create a sub-directory for each performance state */ in em_debug_create_pd()
122 /* Build the list of performance states for this performance domain */ in em_create_perf_table()
126 * lowest performance state of 'dev' above 'freq' and updates in em_create_perf_table()
138 * higher performance states. in em_create_perf_table()
160 /* Compute the cost of each performance state. */ in em_create_perf_table()
283 * em_pd_get() - Return the performance domain for a device
284 * @dev : Device to find the performance domain for
286 * Returns the performance domain to which @dev belongs, or NULL if it doesn't
[all …]
|
| /Linux-v6.1/tools/power/cpupower/bench/ |
| 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-v6.1/Documentation/userspace-api/ |
| 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-v6.1/drivers/perf/hisilicon/ |
| 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-v6.1/Documentation/ABI/testing/ |
| D | sysfs-platform_profile | 13 and performance
14 balanced-performance Balance between performance and low
16 towards performance
17 performance High performance operation
|
| /Linux-v6.1/Documentation/scheduler/ |
| D | sched-energy.rst | 38 performance [inst/s]
48 while still getting 'good' performance. It is essentially an alternative
49 optimization objective to the current performance-only objective for the
51 performance.
78 task/CPU is, and to take this into consideration when evaluating performance vs
84 per 'performance domain' in the system (see Documentation/power/energy-model.rst
85 for futher details about performance domains).
89 scheduler maintains a singly linked list of all performance domains intersecting
95 necessarily match those of performance domains, the lists of different root
99 Let us consider a platform with 12 CPUs, split in 3 performance domains
[all …]
|
