From: Ezequiel Garcia <elezegarcia@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Pekka Enberg <penberg@kernel.org>,
tim.bird@am.sony.com, lizefan@huawei.com,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@redhat.com>, Jason Baron <jbaron@redhat.com>
Subject: Re: [RFC PATCH 1/1] trace: Move trace event enable from fs_initcall to early_initcall
Date: Fri, 24 Aug 2012 08:53:39 -0300 [thread overview]
Message-ID: <CALF0-+XiJBVLRA2ja-JreDgfcrzgzcQJX+JjfB4kiHBgn2-M-g@mail.gmail.com> (raw)
In-Reply-To: <1345214379.3708.29.camel@gandalf.local.home>
Hi Steven,
On Fri, Aug 17, 2012 at 11:39 AM, Steven Rostedt <rostedt@goodmis.org> wrote:
>
> I don't think kmalloc is the issue. The big problem in front of you is
> jump labels. That's what enables and disables trace points, and it gets
> initialized just after memory is set up. You may have to force jump
> labels off when doing early tracing :-/ Although I'm not sure it
> requires allocations.
>
Well, I wasn't thinking *that* early actually. So, I'm trying to enable tracing
at some point after jump_labels (could be near perf_event_init).
Right now, the static ring buffer part is done and I'm having some
problems copying this ring buffer into the *real* one.
Mind giving me another hint?
Thanks a lot for your help so far,
Ezequiel.
prev parent reply other threads:[~2012-08-24 11:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 15:18 [RFC PATCH 1/1] trace: Move trace event enable from fs_initcall to early_initcall Ezequiel Garcia
2012-08-16 21:18 ` Steven Rostedt
2012-08-17 11:01 ` Ezequiel Garcia
2012-08-17 13:55 ` Steven Rostedt
2012-08-17 14:04 ` Ezequiel Garcia
2012-08-17 14:39 ` Steven Rostedt
2012-08-17 20:34 ` Jason Baron
2012-08-24 11:53 ` Ezequiel Garcia [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=CALF0-+XiJBVLRA2ja-JreDgfcrzgzcQJX+JjfB4kiHBgn2-M-g@mail.gmail.com \
--to=elezegarcia@gmail.com \
--cc=fweisbec@gmail.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mingo@redhat.com \
--cc=penberg@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tim.bird@am.sony.com \
/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;
as well as URLs for NNTP newsgroup(s).