Lines Matching refs:performance

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 properly. So, perf_events/Perf performance monitoring is the subject for
56 all kernel security permission checks so perf_events performance
70 as privileged processes with respect to perf_events performance
81 performance analysis of monitored processes or a system. For example,
91 performance monitoring without scope limits. The following steps can be
111    enable members of perf_users group with performance monitoring
123 performance monitoring by using functionality of the configured Perf
139      performance monitoring. Per-user per-cpu perf_event_mlock_kb [2]_
141      performance data. This is the least secure mode since allowed
143      are imposed on *resources* allocated for performance monitoring.
146      *scope* includes per-process and system wide performance monitoring
155      *scope* includes per-process performance monitoring only and
156      excludes system wide performance monitoring. CPU and system events
163      *scope* includes per-process performance monitoring only. CPU and
191 performance monitoring data is governed by the perf_event_mlock_kb [2]_
194 execute performance monitoring. The setting essentially extends the
196 specifically for capturing monitored performance events and related data.
202 wants to start two or more performance monitoring processes, the user is
205 mode option. Otherwise, the first started performance monitoring process
212 perf_events/Perf performance monitoring purpose by providing the Perf