From: Arnd Bergmann <arnd@arndb.de>
To: michal.simek@petalogix.com
Subject: Re: sched_clock - microblaze
Date: Thu, 15 Apr 2010 21:52:03 +0200
User-Agent: KMail/1.13.2 (Linux/2.6.31-19-generic; KDE/4.4.2; x86_64; ; )
Cc: wuzhangjin@gmail.com, Steven Rostedt <rostedt@goodmis.org>,
       Thomas Gleixner <tglx@linutronix.de>,
       LKML <linux-kernel@vger.kernel.org>
References: <4BC728DD.5020404@petalogix.com> <1271355179.20625.107.camel@falcon> <4BC76917.9060604@petalogix.com>
In-Reply-To: <4BC76917.9060604@petalogix.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-Id: <201004152152.03883.arnd@arndb.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 782
Lines: 22

On Thursday 15 April 2010 21:29:27 Michal Simek wrote:
> > sched_clock() {
> >       ftrace_stop();
> >       printk(...);
> >       ftrace_start();
> >       ...
> > }
> 
> But I am describing different problem. sched_clock is called before 
> kernel initialized timers. Microblaze takes all information from DTS 
> that's means that I am not able to read timer because I even don't know 
> where it is. :-(

You could make sched_clock return zero before the clock is probed, it
is very unlikely to be needed before that anyway.

	Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/