processes (reference) in projects: Linux-v6.6

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched refs:processes (Results 1 – 25 of 304) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...13

/Linux-v6.6/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_PERFMON capability are treated 70 as privileged processes with respect to perf_events performance 79 processes but CAP_SYS_ADMIN usage for secure monitoring and observability [all …]
/Linux-v6.6/tools/testing/selftests/powerpc/benchmarks/
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-v6.6/tools/power/cpupower/
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-v6.6/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-v6.6/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, 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
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-v6.6/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-v6.6/Documentation/security/
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. 82 processes (e.g. through a Unix domain socket). Such access rights will then be`
/Linux-v6.6/security/landlock/
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-v6.6/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-dev.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	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)`
/Linux-v6.6/drivers/android/
D	Kconfig	`9 Binder is used in Android for both communication between processes, 14 between said processes.`
/Linux-v6.6/Documentation/userspace-api/
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-v6.6/Documentation/riscv/
D	vector.rst	`16 for processes running under its domain. Calling these interfaces is not 108 processes in form of sysctl knob: 116 * 0: Do not allow Vector code to be executed as the default for new processes. 117 * 1: Allow Vector code to be executed as the default for new processes.`
/Linux-v6.6/Documentation/filesystems/
D	fuse.rst	218 other users' and the super user's processes 221 other users' or the super user's processes 246 undesired behavior in other users' processes, such as: 259 of other users' processes. 273 The solution to this as well as B) is not to allow processes 290 measures, that system processes will never enter non-privileged 295 disables the check for other users' processes. 302 processes in user namespaces where they're unprivileged. For this 307 set, super user's processes have unrestricted access to mounts
/Linux-v6.6/tools/testing/selftests/arm64/fp/
D	TODO	`4 - Ensure ptraced processes actually see the register state visible through`
/Linux-v6.6/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`
/Linux-v6.6/Documentation/admin-guide/hw-vuln/
D	l1d_flush.rst	`59 different processes which are concurrently executing on sibling threads of 62 This can be addressed by controlled placement of processes on physical CPU`

12 3 4 5 6 7 8 9 10 >>...13