From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Steffen Rumler <steffen.rumler.ext@nsn.com>
Cc: Wrobel Heinz-R39252 <r39252@freescale.com>,
Michael Ellerman <michael@ellerman.id.au>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: kernel panic during kernel module load (powerpc specific part)
Date: Wed, 06 Jun 2012 21:32:03 +1000 [thread overview]
Message-ID: <1338982323.7150.165.camel@pasglop> (raw)
In-Reply-To: <4FCF0897.2060405@nsn.com>
On Wed, 2012-06-06 at 09:36 +0200, Steffen Rumler wrote:
>
> how should we continue here ?
> There is the kernel panic, I've described.
>
> Technically, there is an conflict between the code generated by the
> compiler and the loader in module_32.c, at least by using -Os.
> Because the prologue/epilogue is part of the .text and init_module()
> is part of .init.text (in the case __init is applied, as usual),
> a directly reachable call is not always possible.
As we discussed earlier, if you could submit a patch to use r12 instead,
we should merge that.
Cheers,
Ben.
next prev parent reply other threads:[~2012-06-06 11:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 14:33 kernel panic during kernel module load (powerpc specific part) Steffen Rumler
2012-05-30 23:24 ` Michael Ellerman
2012-05-31 7:04 ` Wrobel Heinz-R39252
2012-05-31 11:04 ` Gabriel Paubert
2012-06-01 9:18 ` Benjamin Herrenschmidt
2012-06-01 11:33 ` Wrobel Heinz-R39252
2012-06-04 7:43 ` Steffen Rumler
2012-06-04 10:53 ` Paul Mackerras
2012-06-04 11:03 ` Gabriel Paubert
2012-06-04 22:00 ` Benjamin Herrenschmidt
2012-06-05 10:44 ` Gabriel Paubert
2012-06-05 22:47 ` Benjamin Herrenschmidt
2012-06-05 11:32 ` Gabriel Paubert
2012-06-05 22:14 ` Benjamin Herrenschmidt
2012-06-06 7:36 ` Steffen Rumler
2012-06-06 11:32 ` Benjamin Herrenschmidt [this message]
2012-06-06 14:37 ` [PATCH] " Steffen Rumler
2012-06-21 15:27 ` roger blofeld
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=1338982323.7150.165.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=r39252@freescale.com \
--cc=steffen.rumler.ext@nsn.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).