Home
last modified time | relevance | path

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

/linux/arch/sh/kernel/vsyscall/
H A DMakefile2 obj-y += vsyscall.o vsyscall-syscall.o vsyscall-syms.o
4 $(obj)/vsyscall-syscall.o: $(obj)/vsyscall-trapa.so
7 targets += vsyscall-trapa.o vsyscall-traps.so
8 targets += vsyscall-note.o vsyscall.lds vsyscall-dummy.o
17 vsyscall-flags = -shared -s -Wl,-soname=linux-gate.so.1 -Wl,--hash-style=sysv
19 SYSCFLAGS_vsyscall-trapa.so = $(vsyscall-flags)
21 $(obj)/vsyscall-trapa.so: \
22 $(obj)/vsyscall-%.so: $(obj)/vsyscall.lds $(obj)/vsyscall-%.o FORCE
29 $(obj)/vsyscall-dummy.o: $(obj)/vsyscall.lds \
30 $(obj)/vsyscall-trapa.o $(obj)/vsyscall-note.o FORCE
[all …]
H A D.gitignore2 vsyscall.lds
/linux/Documentation/translations/zh_CN/userspace-api/
H A Dseccomp_filter.rst271 在x86-64上，vsyscall模拟默认开启。（vsyscalls是vDSO调用的传统变体。）目前，模拟
274 - ``SECCOMP_RET_TRAP`` 的返回值会设置一个指向给定vsyscall入口的 ``si_call_addr``，
276 已被模拟，(b) 试图恢复系统调用将再次触发标准vsyscall模拟安全检查，使得恢复系统
288 ``siginfo->si_call_addr`` 。）不要检测其他条件：未来内核可能会改进vsyscall模拟，
289 当前内核在vsyscall=native模式下会有不同表现，但在这些情况下， ``0xF...F600{0,4,8,C}00``
/linux/Documentation/arch/powerpc/
H A 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/arch/x86/entry/vsyscall/
H A Dvsyscall_trace.h3 #define TRACE_SYSTEM vsyscall
28 #define TRACE_INCLUDE_PATH ../../arch/x86/entry/vsyscall/
/linux/arch/x86/kernel/
H A D.gitignore2 vsyscall.lds
/linux/arch/x86/entry/
H A DMakefile18 obj-y += vsyscall/
/linux/tools/testing/selftests/proc/
H A Dproc-empty-vm.c171 static void vsyscall(void) in vsyscall() function
440 vsyscall(); in main()
H A Dproc-pid-vm.c238 static void vsyscall(void) in vsyscall() function
289 vsyscall(); in main()
/linux/kernel/time/
H A DMakefile23 obj-$(CONFIG_HAVE_GENERIC_VDSO) += vsyscall.o
H A DKconfig25 # Timekeeping vsyscall support
/linux/arch/sh/kernel/
H A DMakefile31 obj-$(CONFIG_VSYSCALL) += vsyscall/
/linux/Documentation/arch/x86/
H A Delf_auxvec.rst43 AT_SYSINFO is used for locating the vsyscall entry point. It is not
/linux/Documentation/userspace-api/
H A Dseccomp_filter.rst342 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/Documentation/arch/x86/x86_64/
H A Dmm.rst70 ffffffffff600000 | -10 MB | ffffffffff600fff | 4 kB | legacy vsyscall ABI
129 ffffffffff600000 | -10 MB | ffffffffff600fff | 4 kB | legacy vsyscall ABI
/linux/arch/sh/mm/
H A DKconfig103 bool "Support vsyscall page"
/linux/arch/x86/
H A DKconfig1264 bool "Enable vsyscall emulation" if EXPERT
1268 This enables emulation of the legacy vsyscall page. Disabling
1269 it is roughly equivalent to booting with vsyscall=none, except
1271 tries to use a vsyscall. With this option set to N, offending
2307 prompt "vsyscall table for legacy applications"
2317 line parameter vsyscall=[emulate|xonly|none]. Emulate mode
2330 The kernel traps and emulates calls into the fixed vsyscall
2333 legacy vsyscall area but support for legacy binary
2335 certain uses of the vsyscall area as an ASLR-bypassing
2341 There will be no vsyscall mapping at all. This will
[all …]
/linux/Documentation/virt/kvm/
H A Dapi.rst5679 for a given vCPU. This is typically used for guest vsyscall support.