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: <20110309021930.GB19224@yliu-dev.sh.intel.com>
Date:	Wed, 9 Mar 2011 10:19:30 +0800
From:	Yuanhan Liu <yuanhan.liu@...ux.intel.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Rusty Russell <rusty@...tcorp.com.au>,
	chris <chris@...is-wilson.co.uk>
Subject: Re: [PATCH][RFC] tracing: Enable tracepoints via module parameters

On Tue, Mar 08, 2011 at 09:12:14PM -0500, Steven Rostedt wrote:
> On Wed, 2011-03-09 at 10:01 +0800, Yuanhan Liu wrote:
> 
> > > Users are for testing code ;)
> > 
> > As another end-user, this looks fine (also simple) to me ;)
> 
> Ah, you find this patch I have simple?

Nop, I mean the way to enable it.

> 
> > 
> > > 
> > > But that's a good question. As I wrote this because I'm purging my inbox
> > > and came across Yuanhan Liu's patch set. I'm curios to what Yuanhan's
> > > motivation for this change was.
> > 
> > The motivation of my original patch is simple: try to not miss any trace
> > events. I guess it's a kind of feature that trace(or module) should
> > have ;) 
> 
> Hmm, I probably could add a trace option that simply tells ftrace to
> enable events as modules are loaded.
> 
> 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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ