From: Michal Simek <michal.simek@petalogix.com>
To: steve@digidescorp.com
Cc: Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Wu Zhangjin <wuzhangjin@gmail.com>
Subject: Re: sched_clock - microblaze
Date: Thu, 15 Apr 2010 18:21:22 +0200 [thread overview]
Message-ID: <4BC73D02.5090108@petalogix.com> (raw)
In-Reply-To: <1271343970.3856.7.camel@iscandar.digidescorp.com>
Steven J. Magnani wrote:
> Michal,
>
> On Thu, 2010-04-15 at 16:55 +0200, Michal Simek wrote:
>
>> Is unimplemented sched_clock the reason why ftrace not show fine grain time?
>>
>> Or is there any other thing which is wrong?
>>
>
> I think that's it. On my platform we have a free-running 1 MHz counter
> so I implemented a platform sched_clock for that, and I get nice ftrace
> times.
>
> 0) + 65.000 us | finish_task_switch();
> 0) | lock_sock_nested() {
> 0) + 52.000 us | local_bh_disable();
> 0) + 53.000 us | local_bh_enable();
> 0) ! 264.000 us | }
I don't understand why I should add any "new" free running counter
because we have one free running counter which do it (clocksource timer
- timer1). Or am I missing something?
Thanks for sending your code.
Michal
--
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663
next prev parent reply other threads:[~2010-04-15 16:21 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
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 [this message]
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=4BC73D02.5090108@petalogix.com \
--to=michal.simek@petalogix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=steve@digidescorp.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.