From: Chris Dearman <chris@mips.com>
To: wu zhangjin <wuzhangjin@gmail.com>,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org
Subject: Re: [PATCH] ftrace porting of linux-2.6.29 for mips
Date: Wed, 15 Apr 2009 10:34:59 -0700 [thread overview]
Message-ID: <49E61AC3.2050402@mips.com> (raw)
In-Reply-To: <20090414124001.GB28950@adriano.hkcable.com.hk>
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
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?
Regards
Chris
--
Chris Dearman Desk: +1 650 567 5092 Cell: +1 650 224 8603
MIPS Technologies Inc 1225 Charleston Rd, Mountain View CA 94043
[-- Attachment #2: ftrace.patch --]
[-- Type: text/x-patch, Size: 677 bytes --]
commit dfda04e16fa0cb3929c799d3fdec6b2c1bcc7e51
Author: Chris Dearman <chris@mips.com>
Date: Wed Apr 15 10:26:38 2009 -0700
[MIPS] Generate non-PIC object file when building mcount helper code
Signed-off-by: Chris Dearman <chris@mips.com>
diff --git a/scripts/recordmcount.pl b/scripts/recordmcount.pl
index 8f6118e..ccf4043 100755
--- a/scripts/recordmcount.pl
+++ b/scripts/recordmcount.pl
@@ -213,7 +213,7 @@ if ($arch eq "x86_64") {
$ld .= " -melf".$bits."ltsmip";
}
- $cc .= " -mno-abicalls -mabi=" . $bits . $endian;
+ $cc .= " -mno-abicalls -fno-pic -mabi=" . $bits . $endian;
$ld .= $endian;
if ($bits == 64) {
next prev parent reply other threads:[~2009-04-15 17:35 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 [this message]
2009-04-16 1:40 ` Wu Zhangjin
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=49E61AC3.2050402@mips.com \
--to=chris@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=wuzhangjin@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).