hrtimer: Avoid double seqlock
authorStanislaw Gruszka <stf_xl@wp.pl>
Tue, 25 May 2010 21:49:12 +0000 (23:49 +0200)
committerThomas Gleixner <tglx@linutronix.de>
Wed, 26 May 2010 14:15:37 +0000 (16:15 +0200)
hrtimer_get_softirq_time() has it's own xtime lock protection, so it's
safe to use plain __current_kernel_time() and avoid the double seqlock
loop.

Signed-off-by: Stanislaw Gruszka <stf_xl@wp.pl>
LKML-Reference: <20100525214912.GA1934@r2bh72.net.upc.cz>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
kernel/hrtimer.c

index b9b134b..5c69e99 100644 (file)
@@ -89,7 +89,7 @@ static void hrtimer_get_softirq_time(struct hrtimer_cpu_base *base)
 
        do {
                seq = read_seqbegin(&xtime_lock);
-               xts = current_kernel_time();
+               xts = __current_kernel_time();
                tom = wall_to_monotonic;
        } while (read_seqretry(&xtime_lock, seq));