linux-kernel - Re: [RFC PATCH v2] trace: Move trace event enable from fs_initcall to early

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1346867590.27919.60.camel@gandalf.local.home>
Date:	Wed, 05 Sep 2012 13:53:10 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ezequiel Garcia <elezegarcia@...il.com>
Cc:	linux-kernel@...r.kernel.org, Pekka Enberg <penberg@...nel.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...hat.com>, tim.bird@...sony.com,
	lizefan@...wei.com
Subject: Re: [RFC PATCH v2] trace: Move trace event enable from fs_initcall
 to early_initcall

On Tue, 2012-09-04 at 22:18 -0300, Ezequiel Garcia wrote:
> Hi Steven,
> 
> On 8/17/12, Steven Rostedt <rostedt@...dmis.org> wrote:
> > On Fri, 2012-08-17 at 09:03 -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 trace boot-up allocations.
> >>
> >
> > This is much better, I'll give it some tests and add it to my 3.7 queue.
> >
> 
> Ping? Will you add this to your tree?

Yeah, I haven't been able to test it yet. I've been stuck trying to
figure out bugs on other patches I have queued. I'll let you know when I
do apply it though.

Thanks,

-- 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/