Home
last modified time | relevance | path

Searched refs:vfork (Results 1 – 25 of 26) sorted by relevance

12

/linux-5.19.10/kernel/
Dfork.c1410 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/
Dfork.c110 pid_t pid = vfork(); in bench_vfork()
/linux-5.19.10/tools/testing/selftests/cgroup/
Dtest_freezer.c765 int pid = vfork(); in vfork_fn()
/linux-5.19.10/Documentation/vm/
Dvmalloced-kernel-stacks.rst105 Thread stack allocation is initiated from clone(), fork(), vfork(),
/linux-5.19.10/tools/perf/arch/x86/entry/syscalls/
Dsyscall_64.tbl69 58 common vfork sys_vfork
/linux-5.19.10/arch/x86/entry/syscalls/
Dsyscall_64.tbl69 58 common vfork sys_vfork
Dsyscall_32.tbl204 190 i386 vfork sys_vfork
/linux-5.19.10/arch/alpha/kernel/
Dentry.S812 fork_like vfork
/linux-5.19.10/arch/sh/kernel/syscalls/
Dsyscall.tbl200 190 common vfork sys_vfork
/linux-5.19.10/arch/microblaze/kernel/syscalls/
Dsyscall.tbl200 190 common vfork sys_vfork
/linux-5.19.10/arch/arm/tools/
Dsyscall.tbl206 190 common vfork sys_vfork
/linux-5.19.10/arch/parisc/kernel/syscalls/
Dsyscall.tbl128 113 common vfork sys_vfork_wrapper
/linux-5.19.10/arch/m68k/kernel/syscalls/
Dsyscall.tbl200 190 common vfork __sys_vfork
/linux-5.19.10/arch/sparc/kernel/syscalls/
Dsyscall.tbl90 66 common vfork sys_vfork
/linux-5.19.10/arch/alpha/kernel/syscalls/
Dsyscall.tbl75 66 common vfork alpha_vfork
/linux-5.19.10/arch/s390/kernel/syscalls/
Dsyscall.tbl181 190 common vfork sys_vfork sys_vfork
/linux-5.19.10/tools/perf/arch/powerpc/entry/syscalls/
Dsyscall.tbl243 189 nospu vfork sys_vfork
/linux-5.19.10/tools/perf/arch/s390/entry/syscalls/
Dsyscall.tbl181 190 common vfork sys_vfork sys_vfork
/linux-5.19.10/arch/powerpc/kernel/syscalls/
Dsyscall.tbl243 189 nospu vfork sys_vfork
/linux-5.19.10/Documentation/admin-guide/mm/
Dnommu-mmap.rst12 Memory mapping behaviour also involves the way fork(), vfork(), clone() and
/linux-5.19.10/Documentation/arm64/
Dsme.rst242 fork() or vfork() and the corresponding execve() in typical use).
Dsve.rst281 fork() or vfork() and the corresponding execve() in typical use).
/linux-5.19.10/Documentation/security/keys/
Dcore.rst144 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/
Dadding-syscalls.rst400 (``fork``/``vfork``/``clone``) or even architecture (``execve``/``execveat``)
/linux-5.19.10/arch/parisc/kernel/
Dentry.S1629 fork_like vfork

12