From: yang.shi@linaro.org (Shi, Yang)
To: linux-arm-kernel@lists.infradead.org
Subject: Run armv7 32 bit userspace on aarch64
Date: Mon, 12 Oct 2015 11:41:54 -0700 [thread overview]
Message-ID: <561BFEF2.2030503@linaro.org> (raw)
In-Reply-To: <20151012175026.GL16124@arm.com>
On 10/12/2015 10:50 AM, Will Deacon wrote:
> On Mon, Oct 12, 2015 at 10:38:25AM -0700, Shi, Yang wrote:
>> BTW, it may be related to unaligned address.
>>
>> init[1]: unhandled level 3 translation fault (11) at 0x43acfad3, esr
>> 0x92000047
>> pgd = ffff80007b8be000
>> [43acfad3] *pgd=00000000fb8c5003, *pud=00000000fb8c1003,
>> *pmd=00000000fb8c2003, *pte=0000000000000000
>>
>> The userspace is trying to write to 0x43acfad3, the permission is
>> readonly.
>
> What's the instruction making the access? If it's a store-multiple, then
My aarch64 gdb just shows hex code instead of human readable assembly code.
It is 0xe5c02000.
I just checked the ARMv7 manual, it looks like STRB instruction, so we
can rule this out.
I just figured out it is caused by gcc 5.2 pre-link. It works if I
disable pre-link. The pre-link issue breaks all armv7 userspace even
though it is run on armv7 machines.
Yang
> we don't support that in the arm64 kernel. It would be nice if the 32-bit
> kernel had the same behaviour, but the patch seems to have stalled and
> probably doesn't apply anymore:
>
> http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=7944/1
>
> Will
>
next prev parent reply other threads:[~2015-10-12 18:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 22:46 Run armv7 32 bit userspace on aarch64 Shi, Yang
2015-10-08 11:12 ` Will Deacon
2015-10-09 22:32 ` Shi, Yang
2015-10-10 0:28 ` Shi, Yang
2015-10-10 21:25 ` Arnd Bergmann
2015-10-12 17:26 ` Shi, Yang
2015-10-12 17:38 ` Shi, Yang
2015-10-12 17:50 ` Will Deacon
2015-10-12 18:41 ` Shi, Yang [this message]
2015-10-13 14:18 ` Will Deacon
2015-10-13 16:45 ` Shi, Yang
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=561BFEF2.2030503@linaro.org \
--to=yang.shi@linaro.org \
--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).