linux-kernel - Re: [PATCH 0/1] powerpc: make mcount a stub for dynamic 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] [day] [month] [year] [list]

Date:	Sun, 23 Nov 2008 13:49:58 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org, Paul Mackerras <paulus@...ba.org>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	linuxppc-dev@...abs.org, Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 0/1] powerpc: make mcount a stub for dynamic ftrace


* Steven Rostedt <rostedt@...dmis.org> wrote:

> Paul,
> 
> I have one more patch. I added it to the end of the ppc/ftrace 
> branch. The new way of handling the finding of mcounts means we do 
> not need to do anything in the mcount call itself. It should just be 
> a stub and when ftrace is enabled, it will change the caller sites 
> to call something other than mcount.
> 
> The following patches are in:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> 
>     branch: ppc/ftrace

i've also pulled the ppc/ftrace branch into tip/tracing/powerpc, and 
added it to ftrace-next's linux-next integration rules.

So if Paul gives the green light that the commits have the right 
structure, we can freeze down the branch and the SHA1's and integrate 
it into ftrace-next. (which is integrated in linux-next after the 
powerpc tree so should be all fine in terms of merge ordering)

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