[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.58.0610051438010.31280@gandalf.stny.rr.com>
Date: Thu, 5 Oct 2006 14:38:58 -0400 (EDT)
From: Steven Rostedt <rostedt@...dmis.org>
To: Daniel Walker <dwalker@...sta.com>
cc: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>,
Karim Yaghmour <karim@...rsys.com>,
Andrew Morton <akpm@...l.org>,
Chris Wright <chrisw@...s-sol.org>, fche@...hat.com,
Tom Zanussi <zanussi@...ibm.com>
Subject: Re: [RFC] The New and Improved Logdev (now with kprobes!)
On Thu, 5 Oct 2006, Daniel Walker wrote:
> On Thu, 2006-10-05 at 14:09 -0400, Steven Rostedt wrote:
>
> >
> > My problem with using a timestamp, is that I ran logdev on too many archs.
> > So I need to have a timestamp that I can get to that is always reliable.
> > How does LTTng get the time for different archs? Does it have separate
> > code for each arch?
> >
>
> I just got done updating a patchset that exposes the clocksources from
> generic time to take low level time stamps.. But even without that you
> can just call gettimeofday() directly to get a timestamp .
>
unless you're tracing something that his holding the xtime_lock ;-)
-- Steve
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists