From 057de1bbe0a6e60732c04191b6704f34f339fb02 Mon Sep 17 00:00:00 2001 From: Andi Kleen Date: Fri, 21 Feb 2003 23:56:46 -0800 Subject: [PATCH] [PATCH] Allow xtime_lock declaration in arch specific code for x86-64 x86-64 vsyscalls require mapping the sequence number used by gettimeofday in a magic way, so that userland can access it via vsyscalls for user space time-of-day access. Instead of putting the magic into generic code I just allowed to move it into architecture specific files. --- kernel/timer.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/kernel/timer.c b/kernel/timer.c index b94c6fd8485cf..cabdff7716e77 100644 --- a/kernel/timer.c +++ b/kernel/timer.c @@ -31,6 +31,7 @@ #include #include +#include /* * per-CPU timer vector definitions: @@ -762,7 +763,9 @@ unsigned long wall_jiffies; * This read-write spinlock protects us from races in SMP while * playing with xtime and avenrun. */ +#ifndef ARCH_HAVE_XTIME_LOCK seqlock_t xtime_lock __cacheline_aligned_in_smp = SEQLOCK_UNLOCKED; +#endif unsigned long last_time_offset; /* -- 2.53.0