From: Wu Zhangjin <wuzhangjin@gmail.com>
To: Chris Dearman <chris@mips.com>
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: [PATCH] ftrace porting of linux-2.6.29 for mips
Date: Thu, 16 Apr 2009 09:40:15 +0800 [thread overview]
Message-ID: <1239846015.3538.104.camel@falcon> (raw)
In-Reply-To: <49E61AC3.2050402@mips.com>
On Wed, 2009-04-15 at 10:34 -0700, Chris Dearman wrote:
> Zhang Le wrote:
> > I got ftrace working on fuloong 2f box, finally.
> >
> > The patch could be get here:
> > http://repo.or.cz/w/linux-2.6/linux-loongson.git?a=shortlog;h=refs/heads/linux-2.6.29-stable-ftrace-from-wu
> >
> > It is the second last patch in the above git repo.
>
> I pulled this patch into my local tree to try it out. The attached patch
> removes spurious warnings about linking pic and non-pic object files.
>
> It might be better to pass KBUILD_CFLAGS into the script to get the same
> build options as the rest of the kernel. Was there a reason not to do this?
>
This is a "history problem", for not modify the original source code of
scripts/recordmcount.pl a lot, I just added a line to pass
the "endian" argument in from scripts/Makefile.build
ifdef CONFIG_FTRACE_MCOUNT_RECORD
cmd_record_mcount = perl $(srctree)/scripts/recordmcount.pl "$(ARCH)" \
+ "$(if $(CONFIG_CPU_BIG_ENDIAN),big,little)" \
"$(if $(CONFIG_64BIT),64,32)" \
"$(OBJDUMP)" "$(OBJCOPY)" "$(CC)" "$(LD)" "$(NM)" "$(RM)" "$(MV)"
"$(@)";
endif
but current method is not flexible, currently, the other compile/link
options are ignored or hard-coded there. so, a substitution of
implementation method should be considered. but pass KBUILD_CFLAGS seems
not enough for we need make up the options for cc, ld, objdump, objcopy
tools in scripts/recordmcount.pl. perhaps CFLAGS, LDFLAGS and something
else should be passed from scripts/Makefile.build to
scripts/recordmcount.pl respectively.
thanks!
Wu Zhangjin
next prev parent reply other threads:[~2009-04-16 1:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b00321320904021847w5ab3acb6nd1cd554c251ef8f6@mail.gmail.com>
[not found] ` <20090403113315.GC6629@adriano.hkcable.com.hk>
[not found] ` <b00321320904030503w8fe0165t2aded6727f35e24c@mail.gmail.com>
[not found] ` <b00321320904030551p774d295lce3581c23d9d8c26@mail.gmail.com>
2009-04-03 14:11 ` [PATCH] ftrace porting of linux-2.6.29 for mips Zhang Le
2009-04-03 14:53 ` wu zhangjin
2009-04-03 16:03 ` Zhang Le
2009-04-03 18:06 ` Zhang Le
2009-04-14 12:40 ` Zhang Le
2009-04-15 1:22 ` falcon
2009-04-15 17:34 ` Chris Dearman
2009-04-16 1:40 ` Wu Zhangjin [this message]
2010-04-19 21:40 ` Ralf Baechle
2010-04-20 0:28 ` Ralf Baechle
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=1239846015.3538.104.camel@falcon \
--to=wuzhangjin@gmail.com \
--cc=chris@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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