| /linux/Documentation/admin-guide/ |
| A D | perf-security.rst | 11 monitored processes. The data leakage is possible both in scenarios of
52 To perform security checks, the Linux implementation splits processes
55 processes (whose effective UID is nonzero). Privileged processes bypass
57 monitoring is fully available to privileged processes without access,
70 as privileged processes with respect to perf_events performance
96 Other capabilities being granted to unprivileged processes can
220 or root running processes with CAP_SETPCAP, CAP_SETFCAP [6]_
226 perf_events *scope* and *access* control for unprivileged processes
252 unprivileged processes with CAP_IPC_LOCK capability.
259 unprivileged processes with CAP_IPC_LOCK capability.
[all …]
|
| A D | cgroup-v2.rst | 115 processes. A cgroup controller is usually responsible for
125 existing descendant processes.
451 against internal processes of the parent.
525 all processes under C0 and C1 belong to U0::
894 processes; otherwise, 0.
1152 If a memory cgroup is not populated with processes,
1184 over the high boundary, the processes of the cgroup are
1247 The number of times processes of the cgroup are
1268 The number of processes belonging to this cgroup
1970 Hard limit of number of processes.
[all …]
|
| /linux/tools/testing/selftests/powerpc/benchmarks/ |
| A D | context_switch.c | 279 static int processes; variable
285 if (!processes) in mutex_lock()
306 if (!processes) in mutex_unlock()
323 if (!processes) { in futex_setup()
390 { "process", no_argument, &processes, 1 },
463 if (processes) in main()
475 printf("Using %s with ", processes ? "processes" : "threads"); in main()
|
| /linux/Documentation/admin-guide/cgroup-v1/ |
| A D | pids.rst | 21 number of processes currently in the cgroup is given by pids.current.
25 be smaller than pids.current, or attaching enough processes to the cgroup such
49 Then we create a hierarchy, set limits and attach processes to it::
63 # ( /bin/echo "Here's some processes for you." | cat )
78 # ( /bin/echo "Here's some processes for you." | cat )
83 processes from being forked at all (note that the shell itself counts towards
|
| A D | rdma.rst | 20 set of processes can use. These processes are grouped using RDMA controller.
22 RDMA controller defines two resources which can be limited for processes of a
34 of processes can be limited. Through this controller different rdma
52 of the child processes which shares the address space, rdma resources are
57 deleted after processes migrated. This allow progress migration as well with
|
| /linux/Documentation/security/ |
| A D | landlock.rst | 16 kernel and other processes point of view. Landlock's interface must therefore
19 Landlock is designed to be usable by unprivileged processes while following the
24 Any user can enforce Landlock rulesets on their processes. They are merged and
41 processes.
43 only impact the processes requesting them.
|
| /linux/tools/power/cpupower/ |
| A D | ToDo | 15 - Fork as many processes as there are CPUs in case the
18 -> Execute start measures via the forked processes on
21 -> Execute stop measures via the forked processes on
|
| /linux/Documentation/power/ |
| A D | freezing-of-tasks.rst | 10 The freezing of tasks is a mechanism by which user space processes and some
19 PF_NOFREEZE unset (all user space processes and some kernel threads) are
29 fake signal to all user space processes, and wakes up all the kernel threads.
36 kernel/freezer.c & include/linux/freezer.h). User space processes are generally
43 For user space processes try_to_freeze() is called automatically from the
118 processes, but if any of the kernel threads may cause something like this
160 4. Another reason for freezing tasks is to prevent user space processes from
162 space processes should not notice that such a system-wide operation has
183 space processes:
185 1. Putting processes into an uninterruptible sleep distorts the load average.
[all …]
|
| A D | basic-pm-debugging.rst | 53 - test the freezing of processes
56 - test the freezing of processes and suspending of devices
59 - test the freezing of processes, suspending of devices and platform
63 - test the freezing of processes, suspending of devices, platform
67 - test the freezing of processes, suspending of devices, platform global
77 /sys/power/pm_test (eg. "devices" to test the freezing of processes and
86 Then, the kernel will try to freeze processes, suspend devices, wait a few
88 parameter), resume devices and thaw processes. If "platform" is written to
|
| /linux/Documentation/admin-guide/LSM/ |
| A D | Yama.rst | 16 running state of any of their processes. For example, if one application
18 attach to other running processes (e.g. Firefox, SSH sessions, GPG agent,
43 Firefox's crash handlers, and by Wine for allowing only Wine processes
68 only processes with ``CAP_SYS_PTRACE`` may use ptrace, either with
72 no processes may use ptrace with ``PTRACE_ATTACH`` nor via
|
| A D | SafeSetID.rst | 13 In absence of file capabilities, processes spawned on a Linux system that need
22 While it is possible to implement a tree of processes by giving full
24 tree of processes under non-root user(s) in the first place. Specifically,
44 processes as different uids, but its undesirable to give the daemon a
60 fork(), parent processes specifying custom environment variables or command line
61 args for spawned child processes, or inheritance of file handles across a
114 setgroups() calls for processes with CAP_SETGID restrictions. Until we add
|
| /linux/security/landlock/ |
| A D | Kconfig | 8 Landlock is a sandboxing mechanism that enables processes to restrict
13 configured and enforced by any processes for themselves using the
|
| /linux/tools/power/pm-graph/config/ |
| A D | suspend-x2-proc.cfg | 2 # Proc S3 (Suspend to Mem) x2 test - includes user processes
45 # Display user processes
46 # graph user processes and cpu usage in the timeline (default: false)
|
| A D | freeze.cfg | 45 # Display user processes
46 # graph user processes and cpu usage in the timeline (default: false)
|
| A D | standby.cfg | 45 # Display user processes
46 # graph user processes and cpu usage in the timeline (default: false)
|
| A D | freeze-callgraph.cfg | 46 # Display user processes
47 # graph user processes and cpu usage in the timeline (default: false)
|
| A D | freeze-dev.cfg | 45 # Display user processes
46 # graph user processes and cpu usage in the timeline (default: false)
|
| A D | standby-callgraph.cfg | 46 # Display user processes
47 # graph user processes and cpu usage in the timeline (default: false)
|
| /linux/drivers/android/ |
| A D | Kconfig | 16 Binder is used in Android for both communication between processes,
21 between said processes.
|
| /linux/Documentation/userspace-api/ |
| A D | futex2.rst | 74 A futex can be either private or shared. Private is used for processes that
76 same for all processes. This allows for optimizations in the kernel. To use
78 flag. For processes that doesn't share the same memory space and therefore can
|
| /linux/tools/memory-model/scripts/ |
| A D | README | 41 of processes given a specified timeout, recording the results
54 specified number of processes given a specified timeout, run
|
| /linux/Documentation/admin-guide/mm/damon/ |
| A D | usage.rst | 63 the virtual memory address spaces monitoring can have multiple processes as the
67 values should be pids of the monitoring target processes. For example, below
68 commands set processes having pids 42 and 4242 as the monitoring targets and
94 processes can be covered. However, users can want to limit the monitoring
136 applies those to the target processes. It also counts the total number and
|
| /linux/Documentation/block/ |
| A D | ioprio.rst | 11 processes or process groups, similar to what has been possible with cpu
22 higher priority than any other in the system, processes from this class are
37 IOPRIO_CLASS_IDLE: This is the idle scheduling class, processes running at this
|
| /linux/Documentation/x86/ |
| A D | buslock.rst | 79 "untrusted" user processes on other cores. The hard real time cannot afford
80 to have any bus lock from the untrusted processes to hurt real time
121 allows to identify the offending processes and analyze whether they are
|
| /linux/Documentation/locking/ |
| A D | rt-mutex-design.rst | 35 processes, let's call them processes A, B, and C, where A is the highest
80 - The PI chain is an ordered series of locks and processes that cause
81 processes to inherit priorities from a previous process that is
114 - A list of processes that are blocked on a mutex.
125 differentiate between two processes that are being described together.
131 The PI chain is a list of processes and mutexes that may cause priority
172 For PI to work, the processes at the right end of these chains (or we may
174 than the processes to the left or below in the chain.
274 Now we add 4 processes that run each of these functions separately.
288 This gives us a PI depth of 4 (four processes), but looking at any of the
[all …]
|