Lines Matching full:performance

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
85 denial logging related to usage of performance monitoring and observability.
95 performance analysis of monitored processes or a system. For example,
104 privileged Perf users who are permitted to execute performance monitoring
158 performance monitoring and observability by using functionality of the
174      performance monitoring. Per-user per-cpu perf_event_mlock_kb [2]_
176      performance data. This is the least secure mode since allowed
178      are imposed on *resources* allocated for performance monitoring.
181      *scope* includes per-process and system wide performance monitoring
190      *scope* includes per-process performance monitoring only and
191      excludes system wide performance monitoring. CPU and system events
198      *scope* includes per-process performance monitoring only. CPU and
226 performance monitoring data is governed by the perf_event_mlock_kb [2]_
229 execute performance monitoring. The setting essentially extends the
231 specifically for capturing monitored performance events and related data.
237 wants to start two or more performance monitoring processes, the user is
240 mode option. Otherwise, the first started performance monitoring process
247 perf_events/Perf performance monitoring purpose by providing the Perf