| /Linux-v5.15/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-v5.15/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-v5.15/Documentation/admin-guide/acpi/ |
| D | cppc_sysfs.rst | 4 Collaborative Processor Performance Control (CPPC)
11 performance of a logical processor on a contiguous and abstract performance
12 scale. CPPC exposes a set of registers to describe abstract performance scale,
13 to request performance levels and to measure per-cpu delivered performance.
38 * highest_perf : Highest performance of this processor (abstract scale).
39 * nominal_perf : Highest sustained performance of this processor
41 * lowest_nonlinear_perf : Lowest performance of this processor with nonlinear
43 * lowest_perf : Lowest performance of this processor (abstract scale).
47 The above frequencies should only be used to report processor performance in
51 * feedback_ctrs : Includes both Reference and delivered performance counter.
[all …]
|
| /Linux-v5.15/include/linux/ |
| D | energy_model.h | 14 * struct em_perf_state - Performance state of a performance domain
28 * struct em_perf_domain - Performance domain
29 * @table: List of performance states, in ascending order
30 * @nr_perf_states: Number of performance states
34 * for performance reasons to avoid potential cache
38 * In case of CPU device, a "performance domain" represents a group of CPUs
39 * whose performance is scaled together. All CPUs of a performance domain
40 * must have the same micro-architecture. Performance domains often have
59 * task placement when two Performance Domains might provide similar energy
74 * active_power() - Provide power at the next performance state of
[all …]
|
| /Linux-v5.15/Documentation/admin-guide/pm/ |
| 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-v5.15/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-v5.15/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-v5.15/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-v5.15/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-v5.15/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-v5.15/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-v5.15/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 tristate "ARM SMMUv3 Performance Monitors Extension"
67 Provides support for the ARM SMMUv3 Performance Monitor Counter
76 Provides support for performance monitor unit in ARM DynamIQ Shared
85 Provides support for the DDR performance monitor in i.MX8, which
94 Provides support for the L2 cache performance monitor unit (PMU)
104 Provides support for the L3 cache performance monitor unit (PMU)
123 Say y if you want to use APM X-Gene SoC performance monitors.
|
| /Linux-v5.15/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
87 Drivers are expected to register performance domains into the EM framework by
94 for each performance state. The callback function provided by the driver is free
97 performance domains using cpumask. For other devices than CPUs the last
107 2.3 Accessing performance domains
[all …]
|
| /Linux-v5.15/kernel/power/ |
| D | energy_model.c | 20 * Mutex serializing the registrations of performance domains and letting
71 /* Create the directory of the performance domain */ in em_debug_create_pd()
80 /* Create a sub-directory for each performance state */ in em_debug_create_pd()
120 /* Build the list of performance states for this performance domain */ in em_create_perf_table()
124 * lowest performance state of 'dev' above 'freq' and updates in em_create_perf_table()
136 * higher performance states. in em_create_perf_table()
170 /* Compute the cost of each performance state. */ in em_create_perf_table()
226 * em_pd_get() - Return the performance domain for a device
227 * @dev : Device to find the performance domain for
229 * Returns the performance domain to which @dev belongs, or NULL if it doesn't
[all …]
|
| /Linux-v5.15/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-v5.15/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-v5.15/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-v5.15/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 …]
|
| /Linux-v5.15/kernel/rcu/ |
| D | Kconfig.debug | 27 tristate "performance tests for RCU"
36 This option provides a kernel module that runs performance
40 Say Y here if you want RCU performance tests to be built into
42 Say M if you want the RCU performance tests to build as a module.
74 This option provides a kernel module that runs performance tests
79 Say Y here if you want these performance tests built into the kernel.
126 lifetime and kills performance. Don't try this on large
|
| /Linux-v5.15/tools/testing/selftests/vm/ |
| D | test_vmalloc.sh | 9 # a) analyse performance of vmalloc allocations;
23 # Static templates for performance, stressing and smoke tests.
52 echo "Run performance tests to evaluate how fast vmalloc allocation is."
75 echo "for deep performance analysis as well as stress testing."
84 echo -n "Usage: $0 [ performance ] | [ stress ] | | [ smoke ] | "
108 echo "# Performance analysis"
109 echo "./${DRIVER}.sh performance"
162 if [[ "$1" = "performance" ]]; then
|
| /Linux-v5.15/tools/power/cpupower/man/ |
| D | cpupower-set.1 | 27 its policy for the relative importance of performance versus energy savings to
31 performance and 15 is maximum energy efficiency.
34 when it must select trade-offs between performance and
37 This policy hint does not supersede Processor Performance states
51 Setting the performance bias value on one CPU can modify the setting on
|
| /Linux-v5.15/arch/x86/kernel/cpu/ |
| D | intel_epb.c | 3 * Intel Performance and Energy Bias Hint support.
25 * The Performance and Energy Bias Hint (EPB) allows software to specify its
26 * preference with respect to the power-performance tradeoffs present in the
47 * firmware is 0 ('performance') and at least on some of them that is because
87 * 0 ('performance') at this point, assume that it has not been in intel_epb_restore()
94 pr_warn_once("ENERGY_PERF_BIAS: Set to 'normal', was 'performance'\n"); in intel_epb_restore()
106 "performance",
107 "balance-performance",
|
| /Linux-v5.15/Documentation/admin-guide/mm/ |
| D | numaperf.rst | 9 as CPU cache coherence, but may have different performance. For example,
13 under different domains, or "nodes", based on locality and performance
35 performance when accessing a given memory target. Each initiator-target
55 nodes' access characteristics share the same performance relative to other
65 NUMA Performance
69 be allocated from based on the node's performance characteristics. If
79 The performance characteristics the kernel provides for the local initiators
104 performance characteristics in order to provide large address space of
130 attributes in order to maximize the performance out of such a setup.
|
