From: Steven Rostedt <rostedt@goodmis.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: mingo@elte.hu, fweisbec@gmail.com, linux-kernel@vger.kernel.org,
jreiser@bitwagon.com
Subject: Re: [RFC PATCH] tracing - moving some of recordmcount functionality to binary
Date: Fri, 04 Dec 2009 09:16:14 -0500 [thread overview]
Message-ID: <1259936174.12870.155.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1259934945-18305-1-git-send-email-jolsa@redhat.com>
On Fri, 2009-12-04 at 14:55 +0100, Jiri Olsa wrote:
> hi,
>
> I noticed on some discussion, that it might speedup the FTRACE build process,
> if some of the 'scripts/recordmcount.pl' functionality was done in binary,
> instead of in the script using nm/.objdump output.
>
>
> Before I dive into details, to sum it up:
> - i wrote tool which took over some of the 'recordmcount.pl' stuff
> - with 'allyesconfig' the build was faster about 2 minutes
>
> I'm not sure wether it's worth to continue in this effort,
> but I at least provide some details to have some enclosure.. :)
Actually, John Reiser sent me code a while back to convert the entire
shebang. I like that approach better. I actually just started looking at
it again recently.
The code will need libelf library, and may be arch specific (maybe not).
But if the current system can't compile it or use the binary, I was
going to have the make system default back to the perl script.
I rather keep the perl script intact, and just have an alternative
binary in case that doesn't work.
John,
I haven't touched the code (just dabbled with it). You can post it again
if you want, or I can if you can't find it.
-- Steve
next prev parent reply other threads:[~2009-12-04 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 13:55 Jiri Olsa
2009-12-04 14:16 ` Steven Rostedt [this message]
2009-12-04 17:17 ` John Reiser
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=1259936174.12870.155.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=jreiser@bitwagon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®