Lines Matching refs:monitoring
14 depends on the nature of data that perf_events performance monitoring
21 its topology, used kernel and Perf versions, performance monitoring
43 sensitive process data. If PMUs in some monitoring modes capture values
45 to such monitoring capabilities requires to be ordered and secured
46 properly. So, perf_events/Perf performance monitoring is the subject for
57 monitoring is fully available to privileged processes without access,
71 monitoring and bypass *scope* permissions checks in the kernel.
75 outcome determines whether monitoring is permitted. So unprivileged
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]_
143 are imposed on *resources* allocated for performance monitoring.
146 *scope* includes per-process and system wide performance monitoring
148 monitoring. CPU and system events happened when executing either in
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
180 system, this limit can be easily hit preventing required monitoring
191 performance monitoring data is governed by the perf_event_mlock_kb [2]_
194 execute performance monitoring. The setting essentially extends the
202 wants to start two or more performance monitoring processes, the user is
204 monitoring processes, for example, using the --mmap-pages Perf record
205 mode option. Otherwise, the first started performance monitoring process
212 perf_events/Perf performance monitoring purpose by providing the Perf