| /Linux-v5.4/Documentation/admin-guide/ |
| 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
53 into two categories [6]_ : a) privileged processes (whose effective user
55 processes (whose effective UID is nonzero). Privileged processes bypass
57 monitoring is fully available to privileged processes without access,
60 Unprivileged processes are subject to a full security permission check
66 independently enabled and disabled on per-thread basis for processes and
69 Unprivileged processes with enabled CAP_SYS_ADMIN capability are treated
70 as privileged processes with respect to perf_events performance
73 Unprivileged processes using perf_events system call API is also subject
[all …]
|
| /Linux-v5.4/tools/testing/selftests/powerpc/benchmarks/ |
| D | context_switch.c | 268 static int processes; variable
274 if (!processes) in mutex_lock()
295 if (!processes) in mutex_unlock()
312 if (!processes) { in futex_setup()
379 { "process", no_argument, &processes, 1 },
452 if (processes) in main()
464 printf("Using %s with ", processes ? "processes" : "threads"); in main()
|
| /Linux-v5.4/Documentation/admin-guide/cgroup-v1/ |
| 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
|
| 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-v5.4/Documentation/admin-guide/LSM/ |
| 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,
42 Firefox's crash handlers, and by Wine for allowing only Wine processes
67 only processes with ``CAP_SYS_PTRACE`` may use ptrace, either with
71 no processes may use ptrace with ``PTRACE_ATTACH`` nor via
|
| 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
|
| /Linux-v5.4/Documentation/power/ |
| 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
130 3. The third reason is to prevent user space processes and some kernel threads
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:
[all …]
|
| 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-v5.4/tools/power/pm-graph/config/ |
| 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)
|
| D | freeze.cfg | 45 # Display user processes
46 # graph user processes and cpu usage in the timeline (default: false)
|
| D | standby.cfg | 45 # Display user processes
46 # graph user processes and cpu usage in the timeline (default: false)
|
| D | freeze-callgraph.cfg | 46 # Display user processes
47 # graph user processes and cpu usage in the timeline (default: false)
|
| D | freeze-dev.cfg | 45 # Display user processes
46 # graph user processes and cpu usage in the timeline (default: false)
|
| D | standby-callgraph.cfg | 46 # Display user processes
47 # graph user processes and cpu usage in the timeline (default: false)
|
| D | standby-dev.cfg | 45 # Display user processes
46 # graph user processes and cpu usage in the timeline (default: false)
|
| D | suspend-callgraph.cfg | 46 # Display user processes
47 # graph user processes and cpu usage in the timeline (default: false)
|
| D | suspend-dev.cfg | 45 # Display user processes
46 # graph user processes and cpu usage in the timeline (default: false)
|
| D | suspend.cfg | 45 # Display user processes
46 # graph user processes and cpu usage in the timeline (default: false)
|
| /Linux-v5.4/drivers/android/ |
| D | Kconfig | 16 Binder is used in Android for both communication between processes,
21 between said processes.
|
| /Linux-v5.4/tools/memory-model/scripts/ |
| D | README | 41 of processes given a specified timeout, recording the results
54 specified number of processes given a specified timeout, run
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | mandatory-locking.txt | 32 processes. File locks are applied using the flock() and fcntl() system calls
41 In a perfect world all processes would use and honour a cooperative, or
123 other processes are permitted to read from that region. If any of these
124 processes attempts to write to the region it will block until the lock is
135 any mandatory locks owned by other processes will be rejected with the
167 Not even root can override a mandatory lock, so runaway processes can wreak
|
| /Linux-v5.4/include/linux/sched/ |
| D | user.h | 15 atomic_t processes; /* How many processes does this user have? */ member
|
| /Linux-v5.4/security/keys/ |
| D | Kconfig | 37 This allows the key used for multiple step processes where each step
52 in the sense that they stay around after all processes of that UID
57 LSMs gets to rule on which admin-level processes get to access the
|
| /Linux-v5.4/tools/testing/selftests/android/ion/ |
| D | README | 9 between 2 independent processes.
13 two user space processes, using various heap types.
37 Thus the same kernel buffer is shared among two user space processes using
|
| /Linux-v5.4/Documentation/block/ |
| 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
|
