hrtimer: Avoid double seqlock

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Linux Kernel Mailing List
Date: Friday, May 28, 2010 - 11:59 am

Gitweb:     http://git.kernel.org/linus/174bd1994ec67a6e6191c4ed8e5dac17fa221b84
Commit:     174bd1994ec67a6e6191c4ed8e5dac17fa221b84
Parent:     2abfb9e1d470f7082e5e20e4b11a271a0124211b
Author:     Stanislaw Gruszka <stf_xl@wp.pl>
AuthorDate: Tue May 25 23:49:12 2010 +0200
Committer:  Thomas Gleixner <tglx@linutronix.de>
CommitDate: Wed May 26 16:15:37 2010 +0200

    hrtimer: Avoid double seqlock
    
    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 |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/kernel/hrtimer.c b/kernel/hrtimer.c
index b9b134b..5c69e99 100644
--- a/kernel/hrtimer.c
+++ b/kernel/hrtimer.c
@@ -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));
 
--
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
hrtimer: Avoid double seqlock, Linux Kernel Mailing ..., (Fri May 28, 11:59 am)