public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@petalogix.com>
To: Thomas Gleixner <tglx@linutronix.de>,
	Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>
Cc: Wu Zhangjin <wuzhangjin@gmail.com>
Subject: sched_clock - microblaze
Date: Thu, 15 Apr 2010 16:55:25 +0200	[thread overview]
Message-ID: <4BC728DD.5020404@petalogix.com> (raw)

Hi Thomas and Steven,

I would like to improve time measuring for ftrace (Log below)

I looked at http://lkml.org/lkml/2009/11/16/181
where Thomas suggested to create sched_clock() function.
I used the same solution as Wu proposed but it is not nice.

Is unimplemented sched_clock the reason why ftrace not show fine grain time?

Or is there any other thing which is wrong?

Thanks,
Michal



Dumping ftrace buffer:
---------------------------------
  0) ! 10000.00 us |                                }
  0)   <========== |
  0) ! 10000.00 us |                            }
  0) ! 10000.00 us |                          }
  0)   0.000 us    |                          get_seconds();
  0)   0.000 us    |                          tcp_rcv_rtt_update();
  0)   0.000 us    |                          tcp_ack();
  0)   0.000 us    |                          tcp_rcv_rtt_update();
  0)   0.000 us    |                          tcp_urg();
  0)               |                          tcp_data_queue() {
  0)   0.000 us    |                            __sk_mem_schedule();
  0)   0.000 us    |                            tcp_event_data_recv();
  0)   0.000 us    |                            sock_def_readable();
  0)   0.000 us    |                          }
  0)   0.000 us    |                          tcp_check_space();
  0)               |                          __tcp_ack_snd_check() {


-- 
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

             reply	other threads:[~2010-04-15 14:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-15 14:55 Michal Simek [this message]
2010-04-15 15:04 ` sched_clock - microblaze 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
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=4BC728DD.5020404@petalogix.com \
    --to=michal.simek@petalogix.com \
    --cc=linux-kernel@vger.kernel.org \
    --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