All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: powerpc/ppc64: Allow allmodconfig to build (finally !)
Date: Thu, 12 Jun 2014 05:26:44 -0700	[thread overview]
Message-ID: <20140612122644.GA17249@roeck-us.net> (raw)
In-Reply-To: <1399874254.17624.85.camel@pasglop>

On Mon, May 12, 2014 at 03:57:34PM +1000, Benjamin Herrenschmidt wrote:
> This shuffles code around in exceptions-64s.S in order to
> allow an allmodconfig build to succeed.
> 
> The main problems were:
> 
>  - We have a fixed hole from 0x7000 to 0x8000 for use by FW,
> under some circumstances the code before that would grow too
> big and hit the . = 0x7000
> 
>  - The various attempts at making space in there would trigger
> cases where short conditional branches from assembly would no
> longer be able to reach their target. This is especially nasty
> when these branches reside in alternate feature sections which
> are appended at the end of each .o file
> 
> This fixes it by essentially moving all the "second level"
> exception handlers to after the hole and moving a couple of
> functions near the hole itself so they sit at reachable distance
> of both the first level handlers (before the hole) and the alternate
> feature sections (end of file).
> 
> In the long run, if we start hitting this again, we'll probably
> have to split the file in two, probably at the hole location,
> to keep the alt sections used by the first level handlers close
> to them, and move everything else further away.
> 
> But for now, this will do.
> 
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> 
Hi Ben,

what happened with this patch ?

Thanks,
Guenter

  parent reply	other threads:[~2014-06-12 12:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-12  5:57 [PATCH] powerpc/ppc64: Allow allmodconfig to build (finally !) Benjamin Herrenschmidt
2014-05-13  0:28 ` Guenter Roeck
2014-05-13  9:16   ` Benjamin Herrenschmidt
2014-05-13 12:35     ` Guenter Roeck
2014-05-13 17:17     ` Guenter Roeck
2014-05-14  3:34       ` Stephen Rothwell
2014-05-14  5:16         ` Guenter Roeck
2014-05-14  5:52           ` Alan Modra
2014-05-14 15:34             ` Guenter Roeck
2014-05-15  9:47               ` Alan Modra
2014-05-15 10:46                 ` Guenter Roeck
2014-05-15 12:22                   ` Benjamin Herrenschmidt
2014-05-15 13:09                     ` Guenter Roeck
2014-05-14  5:42         ` Alan Modra
2014-05-13 19:41     ` Guenter Roeck
2014-06-12 12:26 ` Guenter Roeck [this message]
2014-06-12 21:57   ` Benjamin Herrenschmidt
2014-06-12 22:17     ` Guenter Roeck

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=20140612122644.GA17249@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.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 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.