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 performance 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 [7]_ , whose outcome determines whether monitoring is permitted.
93 be provided for processes to make performance monitoring and observability
108 performance monitoring and observability without limits. The following
128    enable members of perf_users group with monitoring and observability
161 performance monitoring and observability by using functionality of the
170 performance monitoring and observability operations are available in the
216 environment where they can use tools employing performance monitoring APIs
231      performance monitoring. Per-user per-cpu perf_event_mlock_kb [2]_
235      are imposed on *resources* allocated for performance monitoring.
238      *scope* includes per-process and system wide performance monitoring
240      monitoring. CPU and system events happened when executing either in
247      *scope* includes per-process performance monitoring only and
248      excludes system wide performance monitoring. CPU and system events
255      *scope* includes per-process performance monitoring only. CPU and
272 system, this limit can be easily hit preventing required monitoring
283 performance monitoring data is governed by the perf_event_mlock_kb [2]_
286 execute performance monitoring. The setting essentially extends the
294 wants to start two or more performance monitoring processes, the user is
296 monitoring processes, for example, using the --mmap-pages Perf record
297 mode option. Otherwise, the first started performance monitoring process
304 perf_events/Perf performance monitoring purpose by providing the Perf