linux-kernel - Re: [RFC] x86: entry_64 - introduce 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.1.10.0812121552360.19351@gandalf.stny.rr.com>
Date:	Fri, 12 Dec 2008 15:52:56 -0500 (EST)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Cyrill Gorcunov <gorcunov@...il.com>
cc:	Steven Rostedt <srostedt@...hat.com>, Ingo Molnar <mingo@...e.hu>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Alexander van Heukelum <heukelum@...tmail.fm>,
	fweisbec <fweisbec@...il.com>
Subject: Re: [RFC] x86: entry_64 - introduce FTRACE_ frame macro


On Fri, 12 Dec 2008, Cyrill Gorcunov wrote:

> [Steven Rostedt - Fri, Dec 12, 2008 at 03:19:27PM -0500]
> | 
> ... 
> | > 
> | > Ah, the patch is on top of -tip e3bdf48
> | 
> | If you have tested this with and without dynamic ftrace, for both the
> | function tracer and the function graph tracer, then you have my...
> | 
> | Acked-by: Steven Rostedt <srostedt@...hat.com>
> | 
> | -- Steve
> ...
> 
> Thanks Steven! Actually just catched a bug :) I placed
> these macros under CONFIG_DYNAMIC_FTRACE but have them
> used even if it was undefined -- will fix shortly.
> 
> Well... I think the macros should be placed in differen
> location (maybe in header) to not overload the source.

You can put them in arch/x86/include/asm/ftrace.h That's assembly safe.

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