On Wed, 2012-09-12 at 09:29 -0300, Ezequiel Garcia wrote:
> Steven,
>
> On Tue, Sep 11, 2012 at 9:34 PM, Steven Rostedt wrote:
> ble(void)
> [...]
> >> + /*
> >> + * Early initialization already enabled ftrace event.
> >> + * Now it's only necessary to create the event directory.
>
Steven,
On Tue, Sep 11, 2012 at 9:34 PM, Steven Rostedt wrote:
ble(void)
[...]
>> + /*
>> + * Early initialization already enabled ftrace event.
>> + * Now it's only necessary to create the event directory.
>> + */
>> for_each_event(call, __start_ftrace_events, __stop_ftr
On Tue, Sep 11, 2012 at 9:34 PM, Steven Rostedt wrote:
> On Sat, 2012-09-08 at 17:01 -0300, Ezequiel Garcia wrote:
>> 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
>>
On Sat, 2012-09-08 at 17:01 -0300, Ezequiel Garcia wrote:
> 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 t
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_
5 matches
Mail list logo