From: Steven Rostedt <srostedt@redhat.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [PATCH 5/5] IA64 dynamic ftrace support
Date: Thu, 08 Jan 2009 17:08:07 +0000 [thread overview]
Message-ID: <1231434487.21980.5.camel@localhost.localdomain> (raw)
In-Reply-To: <1230012500.10933.102.camel@sli10-desk.sh.intel.com>
On Thu, 2009-01-08 at 16:05 +0800, Shaohua Li wrote:
> On Tue, 2009-01-06 at 08:42 +0800, Luck, Tony wrote:
> > > In this way, only one instruction is changed to convert code between nop
> > > and call. This should meet dyn-ftrace's requirement.
> > > But this requires CPU support brl instruction, so dyn-ftrace isn't
> > > supported for old Itanium system. Assume there are quite few such old
> > > system running.
> >
> > Perhaps very few old Merced systems are used for development
> > and performance tuning (the kind of work where ftrace is useful).
> > So not having ftrace support on them might not be too big a loss.
> Tony,
> I simplified the patch to make it more clean, no functional change with
> the one I sent last week. please give it a try and consider merge if
> possible.
> Signed-off-by: Shaohua Li <shaohua.li@intel.com>
> ---
> arch/ia64/Kconfig | 2
> arch/ia64/include/asm/ftrace.h | 13 ++
> arch/ia64/kernel/Makefile | 5
> arch/ia64/kernel/entry.S | 51 ++++++++++
> arch/ia64/kernel/ftrace.c | 206 +++++++++++++++++++++++++++++++++++++++++
> scripts/recordmcount.pl | 7 +
Shaohua,
Are you changes now confined to ia64 (besides the recordmcount.pl)
change? Any changes to the ftrace infrastructure we would like to go
through tip. This will give it proper testing against all archs before
pushing it to mainline.
Please send me any patches outside of arch/ia64 that we can pull in.
This includes the recordmcount.pl patch.
Also, send it to rostedt@goodmis.org that account has my scripts to pull
into git.
Thanks,
-- Steve
next prev parent reply other threads:[~2009-01-08 17:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-23 6:08 [PATCH 5/5] IA64 dynamic ftrace support Shaohua Li
2008-12-23 14:35 ` Steven Rostedt
2008-12-24 0:54 ` Shaohua Li
2008-12-24 1:00 ` Steven Rostedt
2008-12-24 8:08 ` Shaohua Li
2008-12-24 13:29 ` Steven Rostedt
2008-12-24 21:50 ` Keith Owens
2008-12-25 1:08 ` Shaohua Li
2008-12-25 3:54 ` Steven Rostedt
2008-12-25 4:01 ` Shaohua Li
2008-12-26 2:42 ` Shaohua Li
2008-12-31 9:11 ` Shaohua Li
2009-01-06 0:42 ` Luck, Tony
2009-01-08 8:05 ` Shaohua Li
2009-01-08 17:08 ` Steven Rostedt [this message]
2009-01-08 20:25 ` Luck, Tony
2009-01-08 22:24 ` Luck, Tony
2009-01-09 2:42 ` Shaohua Li
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=1231434487.21980.5.camel@localhost.localdomain \
--to=srostedt@redhat.com \
--cc=linux-ia64@vger.kernel.org \
/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