linux-kernel - Re: [PATCH 1/7] tracing/function-graph-tracer: make arch generic push pop functions

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, 18 Feb 2009 02:00:39 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Paul Mackerras <paulus@...ba.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Geoff Levand <geoffrey.levand@...sony.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Steven Rostedt <srostedt@...hat.com>
Subject: Re: [PATCH 1/7] tracing/function-graph-tracer: make arch generic
	push pop functions


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

> Ingo,
> 
> This patch is to make function graph arch generic. But since 
> the PowerPC changes depend on it, we want to push it through 
> the PowerPC tree. But since it touches x86 code, can you give 
> an Acked-by to it?

hm, but it's all ftrace bits. Could this go through the tracing 
tree? That's how it's generally done for most cross-arch 
subsystems. By having it in a separate tree we risk conflicts 
and various logistics problems. It's not like the PPC tree is 
modifying its ftrace.c file all that frequently, right?

	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/