From: John Reiser <jreiser@bitwagon.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Steven Rostedt <srostedt@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: recordmcount commutes with "ld -r"
Date: Mon, 17 Aug 2009 08:52:42 -0700 [thread overview]
Message-ID: <4A897CCA.7030809@bitwagon.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0908171025140.20915@gandalf.stny.rr.com>
On 08/17/2009 07:33 AM, Steven Rostedt wrote:
> On Mon, 10 Aug 2009, John Reiser wrote:
>> recordmcount commutes with "ld -r". ...
> Running the linking on the built-in.o and *.ko files is a good idea.
I'll see what it takes to patch scripts/Makefile.build and any other
build-control file that is required.
>> I noticed another property. Logically, recordmcount could modify a
>> .o file in place. ...
>> I have written recordmcount.c which does such modify-in-place ...
> I would be interested in seeing it. Do you require any of the elf
> libraries to use this? If so, that would make the kernel build
> dependent on having the development elf libraries installed.
No, my recordmcount.c is completely standalone except for libc.so.
I'll sent it to you (and anyone else who asks) separately.
> I've thought about converting recordmcount into a C file before, but I was
> a bit hesitant on rewriting elf routines (although I've done it before
> and they are quite trivial) but even more concerned on breaking other
> archs.
Yes, the major question is whether R_ARM_ABS32, R_IA64_IMM64, R_PPC64_ADDR64,
R_SH_DIR32, R_SPARC_64, R_390_64, and R_390_32 are the correct relocation
enums for a plain address. That will require testers...
--
prev parent reply other threads:[~2009-08-17 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 15:46 recordmcount commutes with "ld -r" John Reiser
2009-08-17 14:33 ` Steven Rostedt
2009-08-17 15:52 ` John Reiser [this message]
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=4A897CCA.7030809@bitwagon.com \
--to=jreiser@bitwagon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=srostedt@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.