| /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 …]
|
| H A D | intel_uncore_frequency_scaling.rst | 17 performance, SoCs have internal algorithms for scaling uncore frequency. These
20 It is possible that users have different expectations of uncore performance and
22 the scaling min/max frequencies via cpufreq sysfs to improve CPU performance.
25 different core and uncore performance at distinct phases and they may want to
27 improve overall performance.
120 The Efficiency Latency Control (ELC) feature improves performance
124 get desired performance.
128 While this may result in the best performance per watt, workload may be
129 expecting higher performance at the expense of power. Consider an
133 target performance.
|
| /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/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 …]
|
| H A 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 further 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/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()
153 memcpy(&(dst_states[i]), &(_pr->performance->states[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()
[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
186 Provides support for the L2 cache performance monitor unit (PMU)
[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
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/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
|
| /linux/Documentation/ABI/testing/ |
| 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/arch/x86/ |
| 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/arm_cspmu/ |
| H A D | Kconfig | 9 Provides support for performance monitoring unit (PMU) devices
18 Provides NVIDIA specific attributes for performance monitoring unit
25 Provides Ampere specific attributes for performance monitoring unit
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-bench.txt | 53 System call performance (throughput).
56 Memory access performance.
79 Suite for evaluating performance of scheduler and IPC mechanisms.
168 Suite for evaluating performance of core system call throughput (both usecs/op and ops/sec metrics).
176 Suite for evaluating performance of simple memory copy in various ways.
200 Suite for evaluating performance of simple memory set in various ways.
256 Suite for evaluating perf's event synthesis performance.
|
| H A D | perf-kvm.txt | 23 a performance counter profile of guest os in realtime
26 'perf kvm record <command>' to record the performance counter profile
39 'perf kvm report' to display the performance counter profile information
42 'perf kvm diff' to displays the performance difference amongst two perf.data
51 'perf kvm stat <command>' to run a command and gather performance counter
77 Collect host side performance profile.
79 Collect guest side performance profile.
|