Home
last modified time | relevance | path

Searched refs:vsyscall (Results 1 – 20 of 20) sorted by relevance

/Linux-v5.15/arch/sh/kernel/vsyscall/
DMakefile2 obj-y += vsyscall.o vsyscall-syscall.o vsyscall-syms.o
4 $(obj)/vsyscall-syscall.o: \
5 $(foreach F,trapa,$(obj)/vsyscall-$F.so)
8 targets += $(foreach F,trapa,vsyscall-$F.o vsyscall-$F.so)
9 targets += vsyscall-note.o vsyscall.lds vsyscall-dummy.o
18 vsyscall-flags = -shared -s -Wl,-soname=linux-gate.so.1 -Wl,--hash-style=sysv
20 SYSCFLAGS_vsyscall-trapa.so = $(vsyscall-flags)
22 $(obj)/vsyscall-trapa.so: \
23 $(obj)/vsyscall-%.so: $(src)/vsyscall.lds $(obj)/vsyscall-%.o FORCE
30 $(obj)/vsyscall-dummy.o: $(src)/vsyscall.lds \
[all …]
D.gitignore2 vsyscall.lds
/Linux-v5.15/arch/x86/entry/vsyscall/
Dvsyscall_trace.h3 #define TRACE_SYSTEM vsyscall
28 #define TRACE_INCLUDE_PATH ../../arch/x86/entry/vsyscall/
/Linux-v5.15/Documentation/powerpc/
Dsyscall64-abi.rst122 vsyscall chapter
125 vsyscall calling sequence matches the syscall calling sequence, with the
130 r0 is not used as an input. The vsyscall is selected by its address.
134 The vsyscall may or may not use the caller's stack frame save areas.
147 The vsyscall is performed with a branch-with-link instruction to the vsyscall
152 vsyscalls will run in the same transactional state as the caller. A vsyscall
/Linux-v5.15/arch/x86/kernel/
D.gitignore2 vsyscall.lds
/Linux-v5.15/arch/x86/entry/
DMakefile18 obj-y += vsyscall/
/Linux-v5.15/kernel/time/
DMakefile20 obj-$(CONFIG_HAVE_GENERIC_VDSO) += vsyscall.o
DKconfig25 # Timekeeping vsyscall support
/Linux-v5.15/arch/sh/kernel/
DMakefile31 obj-$(CONFIG_VSYSCALL) += vsyscall/
/Linux-v5.15/Documentation/x86/
Delf_auxvec.rst43 AT_SYSINFO is used for locating the vsyscall entry point. It is not
/Linux-v5.15/tools/testing/selftests/proc/
Dproc-pid-vm.c226 static void vsyscall(void) in vsyscall() function
261 vsyscall(); in main()
/Linux-v5.15/Documentation/userspace-api/
Dseccomp_filter.rst332 On x86-64, vsyscall emulation is enabled by default. (vsyscalls are
337 the vsyscall entry for the given call and not the address after the
340 trying to resume the syscall will again trigger the standard vsyscall
358 condition: future kernels may improve vsyscall emulation and current
359 kernels in vsyscall=native mode will behave differently, but the
/Linux-v5.15/Documentation/x86/x86_64/
Dmm.rst70 ffffffffff600000 | -10 MB | ffffffffff600fff | 4 kB | legacy vsyscall ABI
129 ffffffffff600000 | -10 MB | ffffffffff600fff | 4 kB | legacy vsyscall ABI
/Linux-v5.15/Documentation/
Ddontdiff260 vsyscall.lds
/Linux-v5.15/arch/sh/
DMakefile203 $(Q)$(MAKE) $(clean)=arch/sh/kernel/vsyscall
/Linux-v5.15/arch/sh/mm/
DKconfig95 bool "Support vsyscall page"
/Linux-v5.15/arch/x86/
DKconfig1206 bool "Enable vsyscall emulation" if EXPERT
1210 This enables emulation of the legacy vsyscall page. Disabling
1211 it is roughly equivalent to booting with vsyscall=none, except
1213 tries to use a vsyscall. With this option set to N, offending
2278 prompt "vsyscall table for legacy applications"
2288 line parameter vsyscall=[emulate|xonly|none].
2299 The kernel traps and emulates calls into the fixed vsyscall
2313 The kernel traps and emulates calls into the fixed vsyscall
2316 legacy vsyscall area but support for legacy binary
2318 certain uses of the vsyscall area as an ASLR-bypassing
[all …]
/Linux-v5.15/Documentation/admin-guide/
Dkernel-parameters.txt6171 vsyscall= [X86-64]
6180 emulated reasonably safely. The vsyscall
6184 emulated reasonably safely. The vsyscall
/Linux-v5.15/Documentation/virt/kvm/
Dapi.rst5001 for a given vCPU. This is typically used for guest vsyscall support.
/Linux-v5.15/
DMAINTAINERS7901 F: include/asm-generic/vdso/vsyscall.h
7903 F: kernel/time/vsyscall.c