public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Muizelaar <jeff@infidigm.net>
To: linux-kernel@vger.kernel.org
Subject: Using sched_clock for mmio-trace
Date: Thu, 15 Feb 2007 20:30:24 -0500	[thread overview]
Message-ID: <20070216013024.GA32287@infidigm.net> (raw)

I've built a tool with the goal of logging mmio writes and reads by
device drivers. See http://nouveau.freedesktop.org/wiki/MmioTrace.

I'd like to add support for recording a time stamp on each read and
write. Unfortunately, I am not sure which clock api I should use.

I had a look at blktrace and saw that it uses 'sched_clock()' for time
stamps. However, this symbol is not exported to modules, and from what
I've read it sounds like its use is discouraged.

The question is, what api should I be using? I need something that can
be called from inside interrupt handlers, and obviously the more
accurate and the lower the overhead the better.

-Jeff

             reply	other threads:[~2007-02-16  1:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-16  1:30 Jeff Muizelaar [this message]
2007-02-16 16:30 ` Using sched_clock for mmio-trace Frank Ch. Eigler
2007-02-16 17:45   ` Daniel Walker
2007-02-16 18:10     ` Jeff Muizelaar
2007-02-16 18:28       ` Daniel Walker
2007-02-16 19:34         ` Jeff Muizelaar
2007-02-16 21:06           ` Daniel Walker
2007-02-16 22:10             ` Jeff Muizelaar
2007-02-16 22:47               ` Daniel Walker
2007-02-17  4:36                 ` Jeff Muizelaar
2007-02-16 18:30   ` Jeff Muizelaar
2007-02-16 18:44     ` Randy Dunlap
2007-02-16 19:55       ` Jeff Muizelaar
2007-02-16 20:03   ` Andi Kleen
2007-02-16 21:26     ` Frank Ch. Eigler
2007-02-17 14:56       ` Andi Kleen
2007-02-17 15:19         ` Thomas Gleixner
2007-02-18 17:20           ` Andi Kleen
2007-02-16 20:02 ` Andi Kleen
2007-02-16 19:40   ` Jeff Muizelaar

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=20070216013024.GA32287@infidigm.net \
    --to=jeff@infidigm.net \
    --cc=linux-kernel@vger.kernel.org \
    /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