[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 11 Nov 2008 23:37:30 +0100
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: David Howells <dhowells@...hat.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
Nicolas Pitre <nico@....org>,
Andrew Morton <akpm@...ux-foundation.org>,
torvalds@...ux-foundation.org, rmk+lkml@....linux.org.uk,
mingo@...e.hu, linux-kernel@...r.kernel.org, ralf@...ux-mips.org,
benh@...nel.crashing.org, paulus@...ba.org, davem@...emloft.net,
mingo@...hat.com, tglx@...utronix.de, rostedt@...dmis.org,
linux-arch@...r.kernel.org
Subject: Re: [PATCH] convert cnt32_to_63 to inline
On Tue, 2008-11-11 at 22:31 +0000, David Howells wrote:
> Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca> wrote:
>
> > @@ -52,18 +57,22 @@ unsigned long long sched_clock(void)
> > ...
> > + preempt_disable_notrace();
>
> Please, no! sched_clock() is called with preemption or interrupts disabled
> everywhere except from some debugging code (lock tracing IIRC). If you need
> to insert this preemption disablement somewhere, please insert it there. At
> least then sched_clock() will be called consistently.
Agreed. You could do a WARN_ON(!in_atomic); in sched_clock() depending
on DEBUG_PREEMPT or something to ensure this.
--
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