| /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
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/include/linux/ |
| H A D | energy_model.h | 15 * struct em_perf_state - Performance state of a performance domain
16 * @performance: CPU performance (capacity) at a given frequency
25 unsigned long performance; member
35 * EM_PERF_STATE_INEFFICIENT: The performance state is inefficient. There is
36 * in this em_perf_domain, another performance state with a higher frequency
43 * struct em_perf_table - Performance states table
46 * @state: List of performance states, in ascending order
55 * struct em_perf_domain - Performance domain
58 * @id: A unique ID number for each performance domain
59 * @nr_perf_states: Number of performance states
[all …]
|
| /linux/drivers/acpi/ |
| H A D | processor_perflib.c | 26 #define ACPI_PROCESSOR_FILE_PERFORMANCE "performance"
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()
113 * 0: success. OSPM is now using the performance state specified.
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()
[all …]
|
| /linux/drivers/perf/ |
| H A D | Kconfig | 3 # Performance Monitor Drivers
6 menu "Performance monitor support"
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
113 Provide support for StarLink Performance Monitor Unit.
114 StarLink Performance Monitor Unit integrates one or more cores with
137 tristate "ARM SMMUv3 Performance Monitors Extension"
141 Provides support for the ARM SMMUv3 Performance Monitor Counter
[all …]
|
| /linux/Documentation/admin-guide/acpi/ |
| H A 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 …]
|
| /linux/Documentation/netlink/specs/ |
| H A D | dev-energymodel.yaml | 23 The performance state is inefficient. There is in this perf-domain,
24 another performance state with a higher frequency but a lower or
48 Information on a single performance domains.
57 A unique ID number for each performance domain.
62 Bitmask of performance domain flags.
69 CPUs that belong to this performance domain.
73 Performance states table.
79 A unique ID number for each performance domain.
88 Performance state of a performance domain.
94 name: performance
[all …]
|
| /linux/Documentation/devicetree/bindings/cpufreq/ |
| H A D | mediatek,mt8196-cpufreq-hw.yaml | 14 frequency scaling (dvfs), and can support several performance domains.
23 - description: OPP tables and control for performance domain 0
24 - description: OPP tables and control for performance domain 1
25 - description: OPP tables and control for performance domain 2
27 "#performance-domain-cells":
33 - "#performance-domain-cells"
47 performance-domains = <&performance 0>;
57 performance-domains = <&performance 1>;
65 performance-domains = <&performance 2>;
76 performance: performance-controller@c2c2034 {
[all …]
|
| 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 | qemu,virtual-cpufreq.yaml | 14 Virtual CPUFreq is a virtualized driver in guest kernels that sends performance
16 is associated with a performance domain which can be shared with other vCPUs.
17 Each performance domain has its own set of registers for performance controls.
26 Address and size of region containing performance controls for each of the
27 performance domains. Regions for each performance domain is placed
30 total number of performance domains.
|
| H A D | apple,cluster-cpufreq.yaml | 15 operating-points-v2 table to define the CPU performance states, with the
45 '#performance-domain-cells':
51 - '#performance-domain-cells'
69 performance-domains = <&cpufreq_e>;
77 performance-domains = <&cpufreq_p>;
117 cpufreq_e: performance-controller@210e20000 {
120 #performance-domain-cells = <0>;
123 cpufreq_p: performance-controller@211e20000 {
126 #performance-domain-cells = <0>;
|
| /linux/tools/power/x86/x86_energy_perf_policy/ |
| H A D | x86_energy_perf_policy.8 | 5 x86_energy_perf_policy \- Manage Energy vs. Performance Policy
18 .RB "value: # | default | performance | balance-performance | balance-power | power"
21 displays and updates energy-performance policy settings specific to
25 While \fBx86_energy_perf_policy\fP can manage energy-performance policy
33 and Processor Performance States (P-states).
36 Further, it allows the OS to influence energy/performance trade-offs where there
87 Set a policy with a normal balance between performance and energy efficiency.
88 The processor will tolerate minor performance compromise
93 .I performance
94 Set a policy for maximum performance,
[all …]
|
| /linux/Documentation/admin-guide/pm/ |
| 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
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 …]
|
| H A 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 …]
|
| H A 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
59 active mode, it uses its own internal performance scaling governor algorithm or
60 allows the hardware to do performance scaling by itself, while in the passive
62 a certain performance scaling algorithm. Which of them will be in effect
91 active mode: ``powersave`` and ``performance``. The way they both operate
97 Namely, if that option is set, the ``performance`` algorithm will be used by
122 HWP + ``performance``
[all …]
|
| /linux/arch/powerpc/include/asm/ |
| H A D | reg_fsl_emb.h | 3 * Contains register definitions for the Freescale Embedded Performance
13 /* Performance Monitor Registers */
37 /* Freescale Book E Performance Monitor APU Registers */
38 #define PMRN_PMC0 0x010 /* Performance Monitor Counter 0 */
39 #define PMRN_PMC1 0x011 /* Performance Monitor Counter 1 */
40 #define PMRN_PMC2 0x012 /* Performance Monitor Counter 2 */
41 #define PMRN_PMC3 0x013 /* Performance Monitor Counter 3 */
42 #define PMRN_PMC4 0x014 /* Performance Monitor Counter 4 */
43 #define PMRN_PMC5 0x015 /* Performance Monitor Counter 5 */
84 #define PMRN_UPMC0 0x000 /* User Performance Monitor Counter 0 */
[all …]
|
| /linux/Documentation/admin-guide/ |
| H A 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/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/arch/x86/events/ |
| H A 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/drivers/cpufreq/ |
| H A D | amd-pstate.h | 18 * union perf_cached - A union to cache performance-related data.
19 * @highest_perf: the maximum performance an individual processor may reach,
26 * @nominal_perf: the maximum sustained performance level of the processor,
28 * @lowest_nonlinear_perf: the lowest performance level at which nonlinear power
30 * @lowest_perf: the absolute lowest performance level of the processor
31 * @min_limit_perf: Cached value of the performance corresponding to policy->min
32 * @max_limit_perf: Cached value of the performance corresponding to policy->max
50 * @aperf: actual performance frequency clock count
51 * @mperf: maximum performance frequency clock count
64 * @cppc_req_cached: cached performance request hints
[all …]
|
| /linux/Documentation/admin-guide/perf/ |
| H A 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/Documentation/ABI/testing/ |
| H A D | sysfs-bus-event_source-devices-hv_gpci | 100 runtime by setting "Enable Performance Information Collection" option.
107 * "-EPERM" : Partition is not permitted to retrieve performance information,
108 required to set "Enable Performance Information Collection" option.
132 runtime by setting "Enable Performance Information Collection" option.
139 * "-EPERM" : Partition is not permitted to retrieve performance information,
140 required to set "Enable Performance Information Collection" option.
164 runtime by setting "Enable Performance Information Collection" option.
171 * "-EPERM" : Partition is not permitted to retrieve performance information,
172 required to set "Enable Performance Information Collection" option.
196 runtime by setting "Enable Performance Information Collection" option.
[all …]
|
| /linux/kernel/power/ |
| H A D | energy_model.c | 23 * Mutex serializing the registrations of performance domains and letting
29 * Manage performance domains with IDs. One can iterate the performance domains
77 DEFINE_EM_DBG_SHOW(performance, performance);
107 debugfs_create_file("performance", 0444, d, &em_dbg[i], in em_debug_create_ps()
147 /* Create the directory of the performance domain */ in em_debug_create_pd()
164 /* Create a sub-directory for each performance state */ in em_debug_create_pd()
207 * @pd : EM performance domain for which this must be done
242 * Calculate the performance value for each frequency with in em_init_performance()
249 table[i].performance = div64_u64(max_cap * table[i].frequency, in em_init_performance()
264 /* Compute the cost of each performance state. */ in em_compute_costs()
[all …]
|
| /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/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 …]
|
| /linux/include/uapi/drm/ |
| H A D | v3d_drm.h | 509 * reset performance queries
512 * points to this extension to define a reset performance submission. This CPU
513 * job will reset the performance queries by resetting the values of the
514 * performance monitors. Moreover, it will reset the syncobj to reset query
520 /* Array of performance queries's syncobjs to indicate its availability */
526 /* Number of performance monitors */
535 * performance query results to a buffer
538 * points to this extension to define a copy performance query submission. This
539 * CPU job will copy the performance queries results to a BO with the offset
563 /* Number of performance monitors */
[all …]
|