| /linux/Documentation/devicetree/bindings/dvfs/ |
| 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:
55 performance: performance-controller@12340000 {
58 #performance-domain-cells = <1>;
61 // The node above defines a performance controller that is a performance
[all …]
|
| /linux/drivers/acpi/ |
| A D | processor_perflib.c | 143 if (!pr || !pr->performance || !pr->performance->state_count) in acpi_processor_get_bios_limit()
313 pr->performance->states = in acpi_processor_get_performance_states()
596 if (pr->performance) { in acpi_processor_preregister_performance()
601 if (!performance || !per_cpu_ptr(performance, i)) { in acpi_processor_preregister_performance()
613 pr->performance = per_cpu_ptr(performance, i); in acpi_processor_preregister_performance()
736 if (pr->performance) { in acpi_processor_register_performance()
741 WARN_ON(!performance); in acpi_processor_register_performance()
743 pr->performance = performance; in acpi_processor_register_performance()
746 pr->performance = NULL; in acpi_processor_register_performance()
769 if (pr->performance) in acpi_processor_unregister_performance()
[all …]
|
| /linux/Documentation/admin-guide/acpi/ |
| A D | cppc_sysfs.rst | 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.
56 * reference_perf : Performance level at which reference performance counter
[all …]
|
| /linux/Documentation/devicetree/bindings/cpufreq/ |
| 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>;
|
| /linux/arch/x86/events/ |
| 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/admin-guide/pm/ |
| 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
547 performance, execute some workload and measure performance and get a baseline
548 performance to compare against.
564 performance using Intel(R) SST-BF.
567 number means better performance::
[all …]
|
| A D | intel_pstate.rst | 17 :doc:`CPU performance scaling subsystem <cpufreq>` in the Linux kernel
30 uses frequencies for identifying operating performance points of CPUs and
117 HWP + ``performance``
142 internal P-state selection logic to be less performance-focused.
162 ``performance``
347 maximum supported performance level (the highest supported `turbo
356 maximum supported performance level (the highest supported `turbo
406 of this mechanism is to improve performance).
531 performance than their policy limits.
620 ``performance``.
[all …]
|
| /linux/Documentation/admin-guide/ |
| 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/power/ |
| 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
84 2.2 Registration of performance domains
107 performance domains using cpumask. For other devices than CPUs the last
129 2.3 Accessing performance domains
136 performance domain.
140 the performance domains, and kept in memory untouched.
142 The energy consumed by a performance domain can be estimated using the
168 performance domain in the Energy Model framework using the (fake) 'foo'
[all …]
|
| /linux/Documentation/ABI/testing/ |
| A D | sysfs-platform_profile | 13 and performance
14 balanced-performance Balance between performance and low
16 towards performance
17 performance High performance operation
|
| A D | sysfs-class-fc_host | 7 performance impact notification (FPIN) event.
15 performance impact notification (FPIN) event.
23 performance impact notification (FPIN) event.
|
| 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/userspace-api/ |
| 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/drivers/xen/ |
| 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/tools/power/cpupower/bench/ |
| 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/hisilicon/ |
| A D | Kconfig | 6 Support for HiSilicon SoC L3 Cache performance monitor, Hydra Home
7 Agent performance monitor and DDR Controller performance monitor.
|
| /linux/tools/perf/Documentation/ |
| A D | perf-bench.txt | 53 System call performance (throughput).
56 Memory access performance.
76 Suite for evaluating performance of scheduler and IPC mechanisms.
146 Suite for evaluating performance of core system call throughput (both usecs/op and ops/sec metrics).
154 Suite for evaluating performance of simple memory copy in various ways.
178 Suite for evaluating performance of simple memory set in various ways.
234 Suite for evaluating perf's event synthesis performance.
|
| 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.
|
| /linux/kernel/rcu/ |
| A 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/Documentation/scheduler/ |
| 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.
85 for futher details about performance domains).
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
160 Each performance domain has three Operating Performance Points (OPPs).
261 result in raising the OPP of the entire performance domain, and that will
363 too complex (too many CPUs, too many performance domains, too many performance
[all …]
|
| /linux/drivers/perf/ |
| A D | Kconfig | 56 Say y if you want to use CPU performance monitors on ARM-based
77 Provides support for performance monitor unit in ARM DynamIQ Shared
86 Provides support for the DDR performance monitor in i.MX8, which
95 Provides support for the L2 cache performance monitor unit (PMU)
105 Provides support for the L3 cache performance monitor unit (PMU)
125 Say y if you want to use APM X-Gene SoC performance monitors.
|
| /linux/include/acpi/ |
| A D | processor.h | 166 u16 performance; member
206 u8 performance:1; member
230 struct acpi_processor_performance *performance; member
251 __percpu *performance);
254 *performance, unsigned int cpu);
|
| /linux/Documentation/admin-guide/mm/ |
| A 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
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.
|
| /linux/Documentation/networking/device_drivers/ethernet/neterion/ |
| A D | s2io.rst | 63 significant performance improvement on certain platforms(SGI Altix,
67 (IA64, Xeon) resulting in noticeable performance improvement(up to 7%
123 good performance::
133 Transmit performance:
164 Receive performance:
173 b. Use 2-buffer mode. This results in large performance boost on
|
| /linux/Documentation/devicetree/bindings/sound/ |
| A D | cirrus,cs4234.yaml | 14 high performance analog to digital conversion, 4 channels of high
15 performance digital to analog conversion for audio, and 1 channel of
19 standard audio grade DAC, with performance specifications identical
|