[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1261406427.4314.155.camel@laptop>
Date: Mon, 21 Dec 2009 15:40:27 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Li Zefan <lizf@...fujitsu.com>
Cc: Ingo Molnar <mingo@...e.hu>, Steven Rostedt <rostedt@...dmis.org>,
Frederic Weisbecker <fweisbec@...il.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] tracing: Fix lockdep warning in global_clock()
On Mon, 2009-12-21 at 15:36 +0800, Li Zefan wrote:
> +++ b/kernel/sched_clock.c
> @@ -250,9 +250,9 @@ unsigned long long cpu_clock(int cpu)
> unsigned long long clock;
> unsigned long flags;
>
> - raw_local_irq_save(flags);
> + local_irq_save(flags);
> clock = sched_clock_cpu(cpu);
> - raw_local_irq_restore(flags);
> + local_irq_restore(flags);
>
> return clock;
> }
> ===============================================
>
> I guess it's still true that lower level functions can take locks?
No, I removed the locks from cpu_clock a while back.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists