From: Daniel Walker <dwalker@mvista.com>
To: Jeff Muizelaar <jeff@infidigm.net>
Cc: "Frank Ch. Eigler" <fche@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Using sched_clock for mmio-trace
Date: Fri, 16 Feb 2007 10:28:50 -0800 [thread overview]
Message-ID: <1171650530.3422.25.camel@imap.mvista.com> (raw)
In-Reply-To: <20070216181027.GC6425@infidigm.net>
On Fri, 2007-02-16 at 13:10 -0500, Jeff Muizelaar wrote:
> On Fri, Feb 16, 2007 at 09:45:21AM -0800, Daniel Walker wrote:
> > I've been working on a patch set (below), to expose the clocksources
> > used by generic time to multiple users . It would allow timestamps from
> > different clocks in a generic way. It's not merged, but I'd appreciate
> > any input either of you might have..
> >
> > ftp://source.mvista.com/pub/dwalker/clocksource/
>
> Is it possible to see the resulting clocksource.h and maybe
> clocksource.c after the patch set? That would make looking at it much
> easier.
Well you could just apply the patch set, but I stuck them in the same
directory as above .. I'll delete them in 24 hours or so ..
At one point I replaced sched_clock() ,
ftp://source.mvista.com/pub/dwalker/clocksource/clocksource-v10/add_generic_sched_clock.patch
The API is similar to that version, and sched_clock was the simplest
user of the API that I've done.
Daniel
next prev parent reply other threads:[~2007-02-16 18:31 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 [this message]
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=1171650530.3422.25.camel@imap.mvista.com \
--to=dwalker@mvista.com \
--cc=fche@redhat.com \
--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®