Lines Matching refs:and
3 Perf Events and tool security
12 direct usage of perf_events system call API [2]_ and over data files
15 units (PMU) [2]_ and Perf collect and expose for performance analysis.
16 Collected system and performance data may be split into several
19 1. System hardware and software configuration data, for example: a CPU
20 model and its cache configuration, an amount of available memory and
21 its topology, used kernel and Perf versions, performance monitoring
25 2. User and kernel module paths and their load addresses with sizes,
26 process and thread names with their PIDs and TIDs, timestamps for
27 captured hardware and software events.
31 (PMC) [8]_ and machine specific registers (MSR) [9]_ that provide
38 RBP on x86_64), process user and kernel space memory addresses and
45 to such monitoring capabilities requires to be ordered and secured
54 ID is 0, referred to as superuser or root), and b) unprivileged
58 scope and resource restrictions.
62 effective GID, and supplementary group list).
66 independently enabled and disabled on per-thread basis for processes and
71 monitoring and bypass *scope* permissions checks in the kernel.
88 Mechanisms of capabilities, privileged capability-dumb files [6]_ and
95 group to Perf tool executable and limit access to the executable for
110 2. Assign the required capabilities to the Perf tool executable file and
134 perf_events/Perf *scope* and *access* control for unprivileged processes
138 Impose no *scope* and *access* restrictions on using perf_events
142 monitored *scope* is maximized and no perf_events specific limits
146 *scope* includes per-process and system wide performance monitoring
147 but excludes raw tracepoints and ftrace function tracepoints
148 monitoring. CPU and system events happened when executing either in
149 user or in kernel space can be monitored and captured for later
155 *scope* includes per-process performance monitoring only and
156 excludes system wide performance monitoring. CPU and system events
158 monitored and captured for later analysis. Per-user per-cpu
163 *scope* includes per-process performance monitoring only. CPU and
165 monitored and captured for later analysis. Per-user per-cpu
196 specifically for capturing monitored performance events and related data.
198 For example, if a machine has eight cores and perf_event_mlock_kb limit
206 allocates all available 4128 KiB and the other processes will fail to
209 RLIMIT_MEMLOCK and perf_event_mlock_kb resource constraints are ignored