public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: Run armv7 32 bit userspace on aarch64
Date: Sat, 10 Oct 2015 23:25:25 +0200	[thread overview]
Message-ID: <6978725.cJktLf4M1X@wuerfel> (raw)
In-Reply-To: <56185B98.2060400@linaro.org>

On Friday 09 October 2015 17:28:08 Shi, Yang wrote:
> On 10/9/2015 3:32 PM, Shi, Yang wrote:
> > On 10/8/2015 4:12 AM, Will Deacon wrote:
> >> On Wed, Oct 07, 2015 at 03:46:57PM -0700, Shi, Yang wrote:
> >>> I'm trying to run armv7 little endian userspace on qemu aarch64 with
> >>> 4.1.x
> >>> kernel. I was told by someone such usecase is valid and I have
> >>> CONFIG_COMPAT
> >>> enabled in my kernel.
> >>>
> >>> But, I ran into the below error. It looks the userspace application is
> >>> trying to write a readonly page. I got the similar failure on arm vfp
> >>> with
> >>> Linaro images (4.1 kernel) too.
> >>>
> >>> Did anyone have tried it recently?
> >>
> >> -rc4 seems to be working fine with Debian Jessie armhf on my Juno boards.
> >>
> >> Do you have a good way of reproducing this with a mainline kernel?
> >
> > It seems a qemu's bug. I can get both ubuntu and openembedded userspace
> > bootup on my LS2085 board with 4.1 kernel.
> 
> Some new findings pointed me to another direction.
> 
> I just tried to build OE userspace with gcc 5.2 (default toolchain in OE 
> now), it fails to boot up with the same error.
> 
> Then I tried the below test on 4.1 kernel:
> 
> Linaro OE userspace image (4.9 toolchain)       Failed
> My OE build with 4.9.3 toolchain                Success
> My OE build with 5.2 toolchain                  Failed
> Ubuntu image                                    Success

Does your kernel have 64KB pages enabled? If it does, most 32-bit user space
won't run, except when building it with relatively new toolchains.

Try running with the default 4KB page size if that is the problem.

	Arnd

  reply	other threads:[~2015-10-10 21:25 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 [this message]
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
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=6978725.cJktLf4M1X@wuerfel \
    --to=arnd@arndb.de \
    --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