Lines Matching full: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 modes requires to be ordered and secured properly.
46 So, perf_events performance monitoring and observability operations are
57 monitoring is fully available to privileged processes without access,
71 monitoring and observability operations, thus, bypass *scope* permissions
73 privilege [13]_ (POSIX 1003.1e: 2.2.2.39) for performance monitoring and
75 perfomance monitoring and observability in the system.
77 For backward compatibility reasons the access to perf_events monitoring and
79 processes but CAP_SYS_ADMIN usage for secure monitoring and observability
85 denial logging related to usage of performance monitoring and observability.
89 outcome determines whether monitoring is permitted. So unprivileged
104 privileged Perf users who are permitted to execute performance monitoring
125    enable members of perf_users group with monitoring and observability
158 performance monitoring and observability by using functionality of the
174      performance monitoring. Per-user per-cpu perf_event_mlock_kb [2]_
178      are imposed on *resources* allocated for performance monitoring.
181      *scope* includes per-process and system wide performance monitoring
183      monitoring. CPU and system events happened when executing either in
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
215 system, this limit can be easily hit preventing required monitoring
226 performance monitoring data is governed by the perf_event_mlock_kb [2]_
229 execute performance monitoring. The setting essentially extends the
237 wants to start two or more performance monitoring processes, the user is
239 monitoring processes, for example, using the --mmap-pages Perf record
240 mode option. Otherwise, the first started performance monitoring process
247 perf_events/Perf performance monitoring purpose by providing the Perf