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] [day] [month] [year] [list]
Message-ID: <1303400071.7181.133.camel@gandalf.stny.rr.com>
Date:	Thu, 21 Apr 2011 11:34:31 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Jiri Olsa <jolsa@...hat.com>, mingo@...hat.com,
	a.p.zijlstra@...llo.nl, linux-kernel@...r.kernel.org,
	Tom Zanussi <tzanussi@...il.com>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Li Zefan <lizf@...fujitsu.com>
Subject: Re: [RFC,PATCH 0/3] trace,perf: enabling ftrace/function tracepoint

On Thu, 2011-04-21 at 17:27 +0200, Frederic Weisbecker wrote:

> So the direction is kinda good but the thing needs to be unglobalized
> (if that word ever exists). Filters need to apply individually to
> each users of the function tracer, that's the trickiest part.
> 
> We also need to catch up with set_ftrace_filter and set_ftrace_notrace
> using filters and triggers, so that we can get rid of the global files
> in the end and have only local effects (per perf_event/ftrace).
> 
> But that's a good start.

Note, As I just finished the last of my "tinkering" jobs, I'm now
starting on my bigger projects. The first being the rewrite of the
ftrace function tracing internals.

I'll start it today, but as I have off tomorrow, and my wife has already
filled all my time up with Honeydew tasks (and this extends into the
weekend), I'll have to continue it next week. But hopefully, if all goes
well, I should have an RFC ready by the end of next week.

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