[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c62985530812130728w12230974u1a19d674b429a3e3@mail.gmail.com>
Date: Sat, 13 Dec 2008 16:28:45 +0100
From: "Frédéric Weisbecker" <fweisbec@...il.com>
To: "Steven Rostedt" <rostedt@...dmis.org>
Cc: "Cyrill Gorcunov" <gorcunov@...il.com>,
"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>
Subject: Re: [RFC] x86: entry_64 - introduce FTRACE_ frame macro
2008/12/13 Steven Rostedt <rostedt@...dmis.org>:
> It could be, but remember, the dynamic ftrace gives the ability to specify
> which function can be chosen.
>
> But on the other hand, I guess it would be fine to have it separate. There
> is no reason that it can not be. I would still keep the dynamic part
> dependent on function tracer. At least for now.
>
> -- Steve
I agree. I don't think it will require much modifications.
I think I will change it for 2.6.30....
--
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