Searched refs:vfork (Results 1 – 25 of 26) sorted by relevance
12
/linux-5.19.10/kernel/ |
D | fork.c | 1410 struct completion *vfork; in complete_vfork_done() local 1413 vfork = tsk->vfork_done; in complete_vfork_done() 1414 if (likely(vfork)) { in complete_vfork_done() 1416 complete(vfork); in complete_vfork_done() 1422 struct completion *vfork) in wait_for_vfork_done() argument 1428 killed = wait_for_completion_killable(vfork); in wait_for_vfork_done() 2618 struct completion vfork; in kernel_clone() local 2675 p->vfork_done = &vfork; in kernel_clone() 2676 init_completion(&vfork); in kernel_clone() 2687 if (!wait_for_vfork_done(p, &vfork)) in kernel_clone() [all …]
|
/linux-5.19.10/tools/testing/selftests/powerpc/benchmarks/ |
D | fork.c | 110 pid_t pid = vfork(); in bench_vfork()
|
/linux-5.19.10/tools/testing/selftests/cgroup/ |
D | test_freezer.c | 765 int pid = vfork(); in vfork_fn()
|
/linux-5.19.10/Documentation/vm/ |
D | vmalloced-kernel-stacks.rst | 105 Thread stack allocation is initiated from clone(), fork(), vfork(),
|
/linux-5.19.10/tools/perf/arch/x86/entry/syscalls/ |
D | syscall_64.tbl | 69 58 common vfork sys_vfork
|
/linux-5.19.10/arch/x86/entry/syscalls/ |
D | syscall_64.tbl | 69 58 common vfork sys_vfork
|
D | syscall_32.tbl | 204 190 i386 vfork sys_vfork
|
/linux-5.19.10/arch/alpha/kernel/ |
D | entry.S | 812 fork_like vfork
|
/linux-5.19.10/arch/sh/kernel/syscalls/ |
D | syscall.tbl | 200 190 common vfork sys_vfork
|
/linux-5.19.10/arch/microblaze/kernel/syscalls/ |
D | syscall.tbl | 200 190 common vfork sys_vfork
|
/linux-5.19.10/arch/arm/tools/ |
D | syscall.tbl | 206 190 common vfork sys_vfork
|
/linux-5.19.10/arch/parisc/kernel/syscalls/ |
D | syscall.tbl | 128 113 common vfork sys_vfork_wrapper
|
/linux-5.19.10/arch/m68k/kernel/syscalls/ |
D | syscall.tbl | 200 190 common vfork __sys_vfork
|
/linux-5.19.10/arch/sparc/kernel/syscalls/ |
D | syscall.tbl | 90 66 common vfork sys_vfork
|
/linux-5.19.10/arch/alpha/kernel/syscalls/ |
D | syscall.tbl | 75 66 common vfork alpha_vfork
|
/linux-5.19.10/arch/s390/kernel/syscalls/ |
D | syscall.tbl | 181 190 common vfork sys_vfork sys_vfork
|
/linux-5.19.10/tools/perf/arch/powerpc/entry/syscalls/ |
D | syscall.tbl | 243 189 nospu vfork sys_vfork
|
/linux-5.19.10/tools/perf/arch/s390/entry/syscalls/ |
D | syscall.tbl | 181 190 common vfork sys_vfork sys_vfork
|
/linux-5.19.10/arch/powerpc/kernel/syscalls/ |
D | syscall.tbl | 243 189 nospu vfork sys_vfork
|
/linux-5.19.10/Documentation/admin-guide/mm/ |
D | nommu-mmap.rst | 12 Memory mapping behaviour also involves the way fork(), vfork(), clone() and
|
/linux-5.19.10/Documentation/arm64/ |
D | sme.rst | 242 fork() or vfork() and the corresponding execve() in typical use).
|
D | sve.rst | 281 fork() or vfork() and the corresponding execve() in typical use).
|
/linux-5.19.10/Documentation/security/keys/ |
D | core.rst | 144 clone, fork, vfork or execve occurs. A new keyring is created only when 148 clone, fork, vfork unless CLONE_THREAD is supplied, in which case it is 152 The session-specific keyring is persistent across clone, fork, vfork and
|
/linux-5.19.10/Documentation/process/ |
D | adding-syscalls.rst | 400 (``fork``/``vfork``/``clone``) or even architecture (``execve``/``execveat``)
|
/linux-5.19.10/arch/parisc/kernel/ |
D | entry.S | 1629 fork_like vfork
|
12