kernel-hacking-2024-linux-s.../arch/x86/vdso
Thomas Gleixner 2ab516575f x86: vdso: Use seqcount instead of seqlock
The update of the vdso data happens under xtime_lock, so adding a
nested lock is pointless. Just use a seqcount to sync the readers.

Reviewed-by: Andy Lutomirski <luto@amacapital.net>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
2012-03-15 18:17:58 -07:00
..
vdso32 x86-32, vdso: On system call restart after SYSENTER, use int $0x80 2011-08-23 16:20:10 -07:00
.gitignore
checkundef.sh
Makefile x86-64: Add --no-undefined to vDSO build 2011-07-13 11:23:09 -07:00
vclock_gettime.c x86: vdso: Use seqcount instead of seqlock 2012-03-15 18:17:58 -07:00
vdso-layout.lds.S
vdso-note.S
vdso.lds.S x86-64: Add time to vDSO 2011-05-24 14:51:29 +02:00
vdso.S x86-64: Pad vDSO to a page boundary 2011-08-04 16:13:34 -07:00
vdso32-setup.c
vdso32.S
vgetcpu.c x86-64: Clean up vdso/kernel shared variables 2011-05-24 14:51:28 +02:00
vma.c Merge branch 'x86-cpu-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip 2011-10-28 05:03:12 -07:00