From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Compiling a kernel for armv5 + armv6
Date: Thu, 3 Mar 2011 13:59:27 +0000 [thread overview]
Message-ID: <20110303135927.GE25891@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20110303132056.GB18351@pengutronix.de>
On Thu, Mar 03, 2011 at 02:20:57PM +0100, Sascha Hauer wrote:
> Doing so currently breaks with:
>
> arch/arm/kernel/entry-armv.S: Assembler messages:
> arch/arm/kernel/entry-armv.S:196: Error: selected processor does not support `strex r1,r2,[sp]'
> arch/arm/kernel/entry-armv.S:228: Error: selected processor does not support `strex r1,r2,[sp]'
> arch/arm/kernel/entry-armv.S:286: Error: selected processor does not support `strex r1,r2,[sp]'
> arch/arm/kernel/entry-armv.S:323: Error: selected processor does not support `strex r1,r2,[sp]'
>
> These are used in svc_exit and restore_user_regs.
>
> Is there a way to fix this or do we have to live with this?
As I've mentioned before, ARMv3-ARMv5 is fine. ARMv6-ARMv7 is fine (with
patches). ARMv5->ARMv6 is too big an architecture change to live together.
Compiling the above file for ARMv6 doesn't fix the problem because then
you'll be executing ARMv6 instructions on ARMv5 CPUs, which will fault.
Omitting those instructions makes ARMv6 behaviour unpredictable - as it
means no barriers could be used, no exclusive operations, etc.
Certainly ARMv5 + ARMv6MP is totally out of the question.
prev parent reply other threads:[~2011-03-03 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 13:20 Compiling a kernel for armv5 + armv6 Sascha Hauer
2011-03-03 13:50 ` saeed bishara
2011-03-03 14:01 ` Sascha Hauer
2011-03-03 13:59 ` Russell King - ARM Linux [this message]
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=20110303135927.GE25891@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).