[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1274752534.22648.186.camel@gandalf.stny.rr.com>
Date: Mon, 24 May 2010 21:55:34 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Iram Shahzad <iram.shahzad@...fujitsu.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: FUNCTION_TRACER: can it be used to trace early bootup functions
On Mon, 2010-05-24 at 15:55 +0900, Iram Shahzad wrote:
> Hi
>
> I would like to know whether the Kernel Function Tracer
> (kernel/trace/trace_functions) be used to trace early kernel
> bootup functions starting from start_kernel?
> My arch is ARM, by the way.
>
> I have done some trials but it doesn't seem to trace early
> bootup functions. I even made it the default tracer replacing
> the nop tracer, but still it doesn't give me trace from
> start_kernel.
>
> Looking at the source code, it seems to me that it starts
> recording data only after its own initialization. So does it
> mean that by design it does not support early tracing?
The main reason it does not support early tracing is that we need memory
management initialized before we can setup tracing. The tracing needs to
go somewhere :-)
With my previous tracer (logdev) I had a way to initialize the ring
buffer via bootmem. This allowed for tracing as soon as bootmem could be
allocated.
It is still feasible to add a way to do function tracing with bootmem, I
just never got around to it.
>
> Please CC me in the reply.
Don't worry, that's the default way for LKML ;-)
-- 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