From: "Frank Ch. Eigler" <fche@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Jeff Muizelaar <jeff@infidigm.net>, linux-kernel@vger.kernel.org
Subject: Re: Using sched_clock for mmio-trace
Date: Fri, 16 Feb 2007 16:26:31 -0500 [thread overview]
Message-ID: <20070216212630.GC27135@redhat.com> (raw)
In-Reply-To: <p73fy95g99w.fsf@bingen.suse.de>
Hi -
On Fri, Feb 16, 2007 at 09:03:23PM +0100, Andi Kleen wrote:
> > We in systemtap land have the same problem, and so far made do with
> > slightly postprocessed per-cpu TSC values.
>
> 90+% likely you're not solving your problem correctly this way.
Yes, it was done as a last resort.
We need facility that we can call from even more demanding contexts
than interrupt handlers, considering that kprobes can be placed nearly
anywhere. This is one of the reasons why we don't just use good old
do_gettimeofday(), since it takes locks and can lead to lock recursion
if parts of itself are probed.
- FChE
next prev parent reply other threads:[~2007-02-16 21:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 1:30 Using sched_clock for mmio-trace 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 [this message]
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=20070216212630.GC27135@redhat.com \
--to=fche@redhat.com \
--cc=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