x86: vdso: Use seqcount instead of seqlock
authorThomas Gleixner <tglx@linutronix.de>
Tue, 28 Feb 2012 19:46:04 +0000 (19:46 +0000)
committerJohn Stultz <john.stultz@linaro.org>
Fri, 16 Mar 2012 01:17:58 +0000 (18:17 -0700)
commit2ab516575f2f273b19d95140d02c54612201e80a
tree26db92249e65754d99759af21fd207507a81cec8
parent6c260d586343f7f78239d90aa9e2cfed02f74ff3
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>
arch/x86/include/asm/vgtod.h
arch/x86/kernel/vsyscall_64.c
arch/x86/vdso/vclock_gettime.c