linux-kernel - Re: [PATCH 2/2] tracing/function-return-tracer: Call prepare_ftrace

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]

Date:	Wed, 12 Nov 2008 19:11:57 -0500 (EST)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Frédéric Weisbecker <fweisbec@...il.com>
cc:	Ingo Molnar <mingo@...e.hu>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] tracing/function-return-tracer: Call prepare_ftrace_return
 by registers


> 
> Hmm... The whole thing is splitted in two levels: the infrastructure
> to trace on call and return (and call
> a return handler) and the higher level tracer.
> The first could be called ftrace_exit because it is waht it does.
> And the second is much more about cost evaluation of functions and so
> could be named function_cost. Its
> functions and structures could have this in their name whereas the low
> level things could have ftrace_exit in
> their name.
> 
> What do you think?

Yeah, I like that.

Ingo, what's your thought on that?

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