From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Steven Rostedt <srostedt@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Alexander van Heukelum <heukelum@fastmail.fm>,
Steven Rostedt <rostedt@goodmis.org>,
fweisbec <fweisbec@gmail.com>
Subject: Re: [RFC] x86: entry_64 - introduce FTRACE_ frame macro
Date: Fri, 12 Dec 2008 23:47:24 +0300 [thread overview]
Message-ID: <20081212204724.GA26194@localhost> (raw)
In-Reply-To: <1229113167.32623.12.camel@localhost.localdomain>
[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@redhat.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.
- Cyrill -
next prev parent reply other threads:[~2008-12-12 20:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 18:41 [RFC] x86: entry_64 - introduce FTRACE_ frame macro Cyrill Gorcunov
2008-12-12 20:19 ` Steven Rostedt
2008-12-12 20:47 ` Cyrill Gorcunov [this message]
2008-12-12 20:52 ` Steven Rostedt
2008-12-12 20:57 ` Cyrill Gorcunov
2008-12-12 20:59 ` Cyrill Gorcunov
2008-12-12 21:22 ` Steven Rostedt
2008-12-12 21:27 ` Cyrill Gorcunov
2008-12-12 21:35 ` Cyrill Gorcunov
2008-12-12 21:41 ` Cyrill Gorcunov
2008-12-12 21:56 ` Steven Rostedt
2008-12-13 8:20 ` Cyrill Gorcunov
2008-12-13 14:46 ` Frédéric Weisbecker
2008-12-13 14:59 ` Steven Rostedt
2008-12-13 15:28 ` Frédéric Weisbecker
2008-12-13 15:16 ` Cyrill Gorcunov
2008-12-13 15:26 ` Frédéric Weisbecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081212204724.GA26194@localhost \
--to=gorcunov@gmail.com \
--cc=fweisbec@gmail.com \
--cc=heukelum@fastmail.fm \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=srostedt@redhat.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox