Re: [tip:perf/core] trace: Move trace event enable from fs_initcallto core_initcall

[Pekka Enberg]

Hi Ezequiel,

On Thu, Sep 27, 2012 at 8:49 AM, tip-bot for Ezequiel Garcia
<elezegarcia@xxxxxxxxx> wrote:
> Commit-ID:  8781915ad2716adcd8cd5cc52cee791fc8b00fdf
> Gitweb:     http://git.kernel.org/tip/8781915ad2716adcd8cd5cc52cee791fc8b00fdf
> Author:     Ezequiel Garcia <elezegarcia@xxxxxxxxx>
> AuthorDate: Wed, 12 Sep 2012 11:47:57 -0300
> Committer:  Steven Rostedt <rostedt@xxxxxxxxxxx>
> CommitDate: Mon, 24 Sep 2012 14:13:02 -0400
>
> trace: Move trace event enable from fs_initcall to core_initcall
>
> This patch splits trace event initialization in two stages:
>  * ftrace enable
>  * sysfs event entry creation
>
> This allows to capture trace events from an earlier point
> by using 'trace_event' kernel parameter and is important
> to trace boot-up allocations.
>
> Note that, in order to enable events at core_initcall,
> it's necessary to move init_ftrace_syscalls() from
> core_initcall to early_initcall.
>
> Link: http://lkml.kernel.org/r/1347461277-25302-1-git-send-email-elezegarcia@xxxxxxxxx
>
> Signed-off-by: Ezequiel Garcia <elezegarcia@xxxxxxxxx>
> Signed-off-by: Steven Rostedt <rostedt@xxxxxxxxxxx>

So what's still needed for perf to be able to trace early boot slab
allocations like kmemtrace used to be able to do?

                        Pekka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/