Searched refs:vsyscall (Results 1 – 24 of 24) sorted by relevance
2 obj-y += vsyscall.o vsyscall-syscall.o vsyscall-syms.o4 $(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.o20 SYSCFLAGS_vsyscall-trapa.so = $(vsyscall-flags)22 $(obj)/vsyscall-trapa.so: \23 $(obj)/vsyscall-%.so: $(src)/vsyscall.lds $(obj)/vsyscall-%.o FORCE30 $(obj)/vsyscall-dummy.o: $(src)/vsyscall.lds \31 $(obj)/vsyscall-trapa.o $(obj)/vsyscall-note.o FORCE[all …]
2 vsyscall.lds
122 vsyscall chapter125 vsyscall calling sequence matches the syscall calling sequence, with the130 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 vsyscall152 vsyscalls will run in the same transactional state as the caller. A vsyscall
3 #define TRACE_SYSTEM vsyscall28 #define TRACE_INCLUDE_PATH ../../arch/x86/entry/vsyscall/
1 …vsyscall.o := /usr/bin/ccache /home/test/workspace/code/optee_3.16/build/../toolchains/aarch64/bin…3 source_kernel/time/vsyscall.o := kernel/time/vsyscall.c5 deps_kernel/time/vsyscall.o := \806 include/vdso/vsyscall.h \807 arch/arm64/include/asm/vdso/vsyscall.h \808 include/asm-generic/vdso/vsyscall.h \813 kernel/time/vsyscall.o: $(deps_kernel/time/vsyscall.o)815 $(deps_kernel/time/vsyscall.o):
25 vsyscall.o/
20 obj-$(CONFIG_HAVE_GENERIC_VDSO) += vsyscall.o
1 …clock.o kernel/time/tick-oneshot.o kernel/time/tick-sched.o kernel/time/vsyscall.o kernel/time/tim…
25 # Timekeeping vsyscall support
18 obj-y += vsyscall/
31 obj-$(CONFIG_VSYSCALL) += vsyscall/
226 static void vsyscall(void) in vsyscall() function261 vsyscall(); in main()
43 AT_SYSINFO is used for locating the vsyscall entry point. It is not
332 On x86-64, vsyscall emulation is enabled by default. (vsyscalls are337 the vsyscall entry for the given call and not the address after the340 trying to resume the syscall will again trigger the standard vsyscall358 condition: future kernels may improve vsyscall emulation and current359 kernels in vsyscall=native mode will behave differently, but the
70 ffffffffff600000 | -10 MB | ffffffffff600fff | 4 kB | legacy vsyscall ABI129 ffffffffff600000 | -10 MB | ffffffffff600fff | 4 kB | legacy vsyscall ABI
260 vsyscall.lds
139 time/vsyscall.o/
1219 bool "Enable vsyscall emulation" if EXPERT1223 This enables emulation of the legacy vsyscall page. Disabling1224 it is roughly equivalent to booting with vsyscall=none, except1226 tries to use a vsyscall. With this option set to N, offending2294 prompt "vsyscall table for legacy applications"2304 line parameter vsyscall=[emulate|xonly|none].2315 The kernel traps and emulates calls into the fixed vsyscall2332 legacy vsyscall area but support for legacy binary2334 certain uses of the vsyscall area as an ASLR-bypassing2340 There will be no vsyscall mapping at all. This will[all …]
95 bool "Support vsyscall page"
980 include/vdso/vsyscall.h \981 arch/arm64/include/asm/vdso/vsyscall.h \982 include/asm-generic/vdso/vsyscall.h \
6221 vsyscall= [X86-64]6230 emulated reasonably safely. The vsyscall6234 emulated reasonably safely. The vsyscall
5187 for a given vCPU. This is typically used for guest vsyscall support.
8035 F: include/asm-generic/vdso/vsyscall.h8037 F: kernel/time/vsyscall.c
Completed in 58 milliseconds