[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070216104415.bca20c4b.randy.dunlap@oracle.com>
Date: Fri, 16 Feb 2007 10:44:15 -0800
From: Randy Dunlap <randy.dunlap@...cle.com>
To: Jeff Muizelaar <jeff@...idigm.net>
Cc: "Frank Ch. Eigler" <fche@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: Using sched_clock for mmio-trace
On Fri, 16 Feb 2007 13:30:14 -0500 Jeff Muizelaar wrote:
> On Fri, Feb 16, 2007 at 11:30:56AM -0500, Frank Ch. Eigler wrote:
> > Jeff Muizelaar <jeff@...idigm.net> writes:
> >
> > > I've built a tool with the goal of logging mmio writes and reads by
> > > device drivers. See http://nouveau.freedesktop.org/wiki/MmioTrace.
> >
> > FWIW, this is exactly a type of add-on trace patch that could be
> > mooted by adoption of the ltt/systemtap "marker" facility. With it,
> > you would not need so much code (e.g. no new user-space tools at all,
> > reuse of common tracing buffer logic, permanently placed hooks) and
> > would probably get more utility.
>
> Is there more information on this "marker" facility? e.g. what is a
> marker? Are they just like tracepoints?
On lkml for the past few days/months.
Look for "Linux Kernel Markers" in the subject line.
Mathieu, do you have a web site for LK Markers?
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
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