Searched refs:vsyscall (Results 1 – 19 of 19) sorted by relevance
| /linux-5.19.10/arch/sh/kernel/vsyscall/ |
| D | Makefile | 2 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 | .gitignore | 2 vsyscall.lds
|
| /linux-5.19.10/arch/x86/entry/vsyscall/ |
| D | vsyscall_trace.h | 3 #define TRACE_SYSTEM vsyscall
28 #define TRACE_INCLUDE_PATH ../../arch/x86/entry/vsyscall/
|
| /linux-5.19.10/Documentation/powerpc/ |
| D | syscall64-abi.rst | 122 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-5.19.10/arch/x86/kernel/ |
| D | .gitignore | 2 vsyscall.lds
|
| /linux-5.19.10/arch/x86/entry/ |
| D | Makefile | 18 obj-y += vsyscall/
|
| /linux-5.19.10/kernel/time/ |
| D | Makefile | 20 obj-$(CONFIG_HAVE_GENERIC_VDSO) += vsyscall.o
|
| D | Kconfig | 25 # Timekeeping vsyscall support
|
| /linux-5.19.10/arch/sh/kernel/ |
| D | Makefile | 31 obj-$(CONFIG_VSYSCALL) += vsyscall/
|
| /linux-5.19.10/Documentation/x86/ |
| D | elf_auxvec.rst | 43 AT_SYSINFO is used for locating the vsyscall entry point. It is not
|
| /linux-5.19.10/tools/testing/selftests/proc/ |
| D | proc-pid-vm.c | 228 static void vsyscall(void) in vsyscall() function
263 vsyscall(); in main()
|
| /linux-5.19.10/Documentation/userspace-api/ |
| D | seccomp_filter.rst | 342 On x86-64, vsyscall emulation is enabled by default. (vsyscalls are
347 the vsyscall entry for the given call and not the address after the
350 trying to resume the syscall will again trigger the standard vsyscall
368 condition: future kernels may improve vsyscall emulation and current
369 kernels in vsyscall=native mode will behave differently, but the
|
| /linux-5.19.10/Documentation/x86/x86_64/ |
| D | mm.rst | 70 ffffffffff600000 | -10 MB | ffffffffff600fff | 4 kB | legacy vsyscall ABI
129 ffffffffff600000 | -10 MB | ffffffffff600fff | 4 kB | legacy vsyscall ABI
|
| /linux-5.19.10/Documentation/ |
| D | dontdiff | 261 vsyscall.lds
|
| /linux-5.19.10/arch/sh/mm/ |
| D | Kconfig | 95 bool "Support vsyscall page"
|
| /linux-5.19.10/arch/x86/ |
| D | Kconfig | 1232 bool "Enable vsyscall emulation" if EXPERT
1236 This enables emulation of the legacy vsyscall page. Disabling
1237 it is roughly equivalent to booting with vsyscall=none, except
1239 tries to use a vsyscall. With this option set to N, offending
2314 prompt "vsyscall table for legacy applications"
2324 line parameter vsyscall=[emulate|xonly|none]. Emulate mode
2337 The kernel traps and emulates calls into the fixed vsyscall
2340 legacy vsyscall area but support for legacy binary
2342 certain uses of the vsyscall area as an ASLR-bypassing
2348 There will be no vsyscall mapping at all. This will
[all …]
|
| /linux-5.19.10/Documentation/admin-guide/ |
| D | kernel-parameters.txt | 6612 vsyscall= [X86-64]
6621 emulated reasonably safely. The vsyscall
6625 emulated reasonably safely. The vsyscall
|
| /linux-5.19.10/Documentation/virt/kvm/ |
| D | api.rst | 5418 for a given vCPU. This is typically used for guest vsyscall support.
|
| /linux-5.19.10/ |
| D | MAINTAINERS | 8451 F: include/asm-generic/vdso/vsyscall.h
8453 F: kernel/time/vsyscall.c
|