mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Jeff Muizelaar <jeff@infidigm.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Using sched_clock for mmio-trace
Date: 16 Feb 2007 21:02:44 +0100	[thread overview]
Message-ID: <p73k5yhg9az.fsf@bingen.suse.de> (raw)
In-Reply-To: <20070216013024.GA32287@infidigm.net>

Jeff Muizelaar <jeff@infidigm.net> writes:
> 
> 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.

Use do_gettimeofday(). sched_clock() is not for general use
and only for some very limited use cases and will give you
unexpected results in several cases.

There are a few cases where gtod is still a little slow, but these
are being addressed. In many cases it is fast. In some hardware
it stays slow, but there is not much that can be done about that
because of the hardware design.

It works fine from interrupt handlers and other strange contexts. 

-Andi

  parent reply	other threads:[~2007-02-16 19:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-16  1:30 Jeff Muizelaar
2007-02-16 16:30 ` 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 [this message]
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=p73k5yhg9az.fsf@bingen.suse.de \
    --to=andi@firstfloor.org \
    --cc=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

all inboxes | Powered by JetHome®