From: Steven Rostedt <rostedt@goodmis.org>
To: Iram Shahzad <iram.shahzad@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: FUNCTION_TRACER: can it be used to trace early bootup functions
Date: Mon, 24 May 2010 21:55:34 -0400 [thread overview]
Message-ID: <1274752534.22648.186.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <06EE497F774E482693005209CB740D6A@rainbow>
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
prev parent reply other threads:[~2010-05-25 1:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 6:55 Iram Shahzad
2010-05-24 23:32 ` Tim Bird
2010-05-25 0:58 ` Iram Shahzad
2010-05-25 1:55 ` Steven Rostedt [this message]
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=1274752534.22648.186.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=iram.shahzad@jp.fujitsu.com \
--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®