| /OK3568_Linux_fs/kernel/drivers/acpi/ |
| H A D | processor_perflib.c | 26 #define ACPI_PROCESSOR_FILE_PERFORMANCE "performance"
83 if (ppc >= pr->performance->state_count || in acpi_processor_get_platform_limit()
88 pr->performance->states[ppc].core_frequency * 1000); in acpi_processor_get_platform_limit()
102 * 0: success. OSPM is now using the performance state specificed.
116 if (ignore_ppc || !pr->performance) { in acpi_processor_ppc_has_changed()
146 if (!pr || !pr->performance || !pr->performance->state_count) in acpi_processor_get_bios_limit()
148 *limit = pr->performance->states[pr->performance_platform_limit]. in acpi_processor_get_bios_limit()
228 memcpy(&pr->performance->control_register, obj.buffer.pointer, in acpi_processor_get_performance_control()
245 memcpy(&pr->performance->status_register, obj.buffer.pointer, in acpi_processor_get_performance_control()
314 ACPI_DEBUG_PRINT((ACPI_DB_INFO, "Found %d performance states\n", in acpi_processor_get_performance_states()
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/acpi/ |
| H A D | cppc_sysfs.rst | 4 Collaborative Processor Performance Control (CPPC)
11 performance of a logical processor on a contigious 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 …]
|
| /OK3568_Linux_fs/kernel/include/linux/ |
| H A D | energy_model.h | 14 * em_perf_state - Performance state of a performance domain
29 * em_perf_domain - Performance domain
30 * @table: List of performance states, in ascending order
31 * @nr_perf_states: Number of performance states
35 * for performance reasons to avoid potential cache
39 * In case of CPU device, a "performance domain" represents a group of CPUs
40 * whose performance is scaled together. All CPUs of a performance domain
41 * must have the same micro-architecture. Performance domains often have
60 * task placement when two Performance Domains might provide similar energy
75 * active_power() - Provide power at the next performance state of
[all …]
|
| /OK3568_Linux_fs/kernel/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 | 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
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``
121 Energy-Performance Preference (EPP) knob (if supported) or its
[all …]
|
| H A 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",
|
| /OK3568_Linux_fs/kernel/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 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 …]
|
| /OK3568_Linux_fs/kernel/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 …]
|
| /OK3568_Linux_fs/kernel/arch/powerpc/include/asm/ |
| H A 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 …]
|
| /OK3568_Linux_fs/kernel/drivers/gpu/drm/msm/disp/dpu1/ |
| H A 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 …]
|
| /OK3568_Linux_fs/kernel/Documentation/power/ |
| H A D | energy-model.rst | 11 the power consumed by devices at various performance levels, and the kernel
53 'performance domain' in the system. A performance domain is a group of CPUs
54 whose performance is scaled together. Performance domains generally have a
55 1-to-1 mapping with CPUFreq policies. All CPUs in a performance domain are
56 required to have the same micro-architecture. CPUs in different performance
69 2.2 Registration of performance domains
72 Drivers are expected to register performance domains into the EM framework by
79 for each performance state. The callback function provided by the driver is free
82 performance domains using cpumask. For other devices than CPUs the last
89 2.3 Accessing performance domains
[all …]
|
| /OK3568_Linux_fs/kernel/kernel/power/ |
| H A 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()
119 /* Build the list of performance states for this performance domain */ in em_create_perf_table()
123 * lowest performance state of 'dev' above 'freq' and updates in em_create_perf_table()
135 * higher performance states. in em_create_perf_table()
157 /* Compute the cost of each performance state. */ in em_create_perf_table()
219 * em_pd_get() - Return the performance domain for a device
220 * @dev : Device to find the performance domain for
222 * Returns the performance domain to which @dev belongs, or NULL if it doesn't
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/perf/ |
| H A 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.
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/kernel/drivers/gpu/arm/bifrost/csf/ipa_control/ |
| H A D | mali_kbase_csf_ipa_control.h | 28 * Maximum index accepted to configure an IPA Control performance counter.
33 * struct kbase_ipa_control_perf_counter - Performance counter description
42 * @type: Type of counter block for performance counter.
43 * @idx: Index of the performance counter inside the block.
48 * a performance counter that they intend to read. The counter is identified
85 * @perf_counters: Array of performance counters the client intends to read.
89 * @num_counters: Number of performance counters. It cannot exceed the total
97 * performance counters it intends to read, and specifying a scaling factor
98 * and whether normalization is requested for each performance counter.
124 * kbase_ipa_control_query - Query performance counters
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/gpu/arm/bifrost/ipa/backend/ |
| H A D | mali_kbase_ipa_counter_jm.c | 28 /* Performance counter blocks base offsets */
49 * kbase_g7x_power_model_get_jm_counter() - get performance counter offset
52 * @counter_block_offset: offset in bytes of the performance counter inside
55 * Return: Block offset in bytes of the required performance counter.
64 * kbase_g7x_power_model_get_memsys_counter() - get performance counter offset
67 * @counter_block_offset: offset in bytes of the performance counter inside
70 * Return: Block offset in bytes of the required performance counter.
75 /* The base address of Memory System performance counters is always the same, although their number in kbase_g7x_power_model_get_memsys_counter()
82 * kbase_g7x_power_model_get_sc_counter() - get performance counter offset
85 * @counter_block_offset: offset in bytes of the performance counter inside
[all …]
|
| /OK3568_Linux_fs/kernel/include/uapi/gpu/arm/bifrost/ |
| H A D | mali_kbase_hwcnt_reader.h | 110 * @PRFCNT_LIST_TYPE_ENUM: Enumeration of performance counters.
150 * enum prfcnt_block_type - Type of performance counter block.
166 * enum prfcnt_set - Type of performance counter block set.
180 * struct prfcnt_enum_block_counter - Performance counter block descriptor.
181 * @block_type: Type of performance counter block.
223 * struct prfcnt_enum_item - Performance counter enumeration item.
227 * @u.block_counter: Performance counter block descriptor.
229 * @u.sample_info: Performance counter sample information descriptor.
275 * @block_type: Type of performance counter block.
278 * @enable_mask: Bitmask that indicates which performance counters to enable.
[all …]
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/kernel/Documentation/scheduler/ |
| 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 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 …]
|
| /OK3568_Linux_fs/kernel/drivers/soc/rockchip/ |
| H A D | Kconfig | 113 bool "Rockchip performance configuration support"
117 and performance.
120 int "Rockchip performance default level"
125 Select default performance level:
127 0 for low-performance (powersave),
128 1 for normal performance,
129 2 for high-performance.
139 In order to meet high performance and low power requirements, a power
150 the chip performance variance caused by chip process, voltage and
|
| /OK3568_Linux_fs/kernel/tools/testing/selftests/vm/ |
| H A D | test_vmalloc.sh | 9 # a) analyse performance of vmalloc allocations;
22 # Static templates for performance, stressing and smoke tests.
51 echo "Run performance tests to evaluate how fast vmalloc allocation is."
74 echo "for deep performance analysis as well as stress testing."
83 echo -n "Usage: $0 [ performance ] | [ stress ] | | [ smoke ] | "
107 echo "# Performance analysis"
108 echo "./${DRIVER}.sh performance"
161 if [[ "$1" = "performance" ]]; then
|
| /OK3568_Linux_fs/kernel/kernel/rcu/ |
| H 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.
149 lifetime and kills performance. Don't try this on large
|
| /OK3568_Linux_fs/buildroot/dl/unixbench/git/ |
| H A D | README.md | 5 The purpose of UnixBench is to provide a basic indicator of the performance of a Unix-like system; …
6 tests are used to test various aspects of the system's performance. These test results are then com…
10 Some very simple graphics tests are included to measure the 2D and 3D graphics performance of the s…
16 * the performance of your system when running a single task
17 * the performance of your system when running multiple tasks
49 …old Weicker in 1984. This benchmark is used to measure and compare the performance of computers. T…
85 …gh idea of the system's 2D and 3D graphics performance. Bear in mind, of course, that the reported…
|
| /OK3568_Linux_fs/kernel/arch/x86/kernel/cpu/ |
| H A 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",
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/mm/ |
| H 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
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.
|