From: Ingo Molnar <mingo@elte.hu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linuxppc-dev@ozlabs.org, linux-next@vger.kernel.org,
Paul Mackerras <paulus@samba.org>,
Alan Modra <amodra@bigpond.net.au>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: linux-next: powerpc build failure
Date: Thu, 12 Jun 2008 09:16:12 +0200 [thread overview]
Message-ID: <20080612071612.GB28590@elte.hu> (raw)
In-Reply-To: <20080612170505.6049fa75.sfr@canb.auug.org.au>
* Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > It is, but you need to pass --relax to enable generation of the
> > trampolines.
>
> So I tried this (added --relax to LDFLAGS_vmlinux if CONFIG FTRACE was
> set) and got this;
>
> /usr/bin/ld: --relax and -r may not be used together
>
> So, I will disable FTRACE on powerpc for now by removing HAVE_FTRACE
> from being selected in arch/powerpc/Kconfig.
ugh, please do that hack only privately in your allyesconfig testing and
do not commit that change to linux-next!
It's not an ftrace bug, this problem is a limitation/bug of the powerpc
architecture and it appears to me that any kernel feature that brings
the allyesconfig text size above 32MB on powerpc will trigger this build
failure.
A few months ago arch/x86 triggered an allyesconfig text size limitation
at 40MB image size (on 64-bit) and we fixed it instead of disabling the
feature/driver that happened to bring the image size above 40MB. See
these commits:
-------->
commit 88f3aec7afd9ae3e6f6d221801996b69aad1e3a4
Author: Ingo Molnar <mingo@elte.hu>
Date: Thu Feb 21 11:04:11 2008 +0100
x86: fix spontaneous reboot with allyesconfig bzImage
commit 85eb69a16aab5a394ce043c2131319eae35e6493
Author: Ingo Molnar <mingo@elte.hu>
Date: Thu Feb 21 12:50:51 2008 +0100
x86: increase the kernel text limit to 512 MB
<--------
Ingo
next prev parent reply other threads:[~2008-06-12 7:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 9:27 linux-next: powerpc build failure Stephen Rothwell
2008-06-11 9:59 ` Ingo Molnar
2008-06-12 1:38 ` Paul Mackerras
2008-06-12 5:33 ` Alan Modra
2008-06-12 7:05 ` Stephen Rothwell
2008-06-12 7:16 ` Ingo Molnar [this message]
2008-06-12 7:27 ` Stephen Rothwell
2008-06-12 7:47 ` Ingo Molnar
2008-06-12 7:23 ` Benjamin Herrenschmidt
2008-06-12 7:24 ` Stephen Rothwell
2008-06-12 18:12 ` Sam Ravnborg
2008-06-12 8:15 ` Alan Modra
-- strict thread matches above, loose matches on Subject: below --
2008-06-10 6:54 Stephen Rothwell
2008-06-10 7:20 ` Benjamin Herrenschmidt
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=20080612071612.GB28590@elte.hu \
--to=mingo@elte.hu \
--cc=amodra@bigpond.net.au \
--cc=hpa@zytor.com \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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).