public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: michal.simek@petalogix.com
Cc: wuzhangjin@gmail.com, Steven Rostedt <rostedt@goodmis.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: sched_clock - microblaze
Date: Thu, 15 Apr 2010 21:52:03 +0200	[thread overview]
Message-ID: <201004152152.03883.arnd@arndb.de> (raw)
In-Reply-To: <4BC76917.9060604@petalogix.com>

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

  reply	other threads:[~2010-04-15 19:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-15 14:55 sched_clock - microblaze Michal Simek
2010-04-15 15:04 ` Steven Rostedt
2010-04-15 16:32   ` Michal Simek
2010-04-15 18:12     ` Wu Zhangjin
2010-04-15 19:29       ` Michal Simek
2010-04-15 19:52         ` Arnd Bergmann [this message]
2010-04-16  6:23           ` Michal Simek
2010-04-16  8:37             ` Arnd Bergmann
2010-04-16  9:11               ` Michal Simek
2010-04-15 15:06 ` Steven J. Magnani
2010-04-15 16:21   ` Michal Simek
2010-04-15 18:26     ` Thomas Gleixner
2010-04-15 17:18 ` Wu Zhangjin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201004152152.03883.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@petalogix.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=wuzhangjin@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox