From: Laurent Vivier <laurent@vivier.eu>
To: Michael Weiser <michael.weiser@gmx.de>, qemu-devel@nongnu.org
Cc: Riku Voipio <riku.voipio@iki.fi>
Subject: Re: [Qemu-devel] [PATCH 0/4] Add aarch64_be-linux-user target
Date: Tue, 19 Dec 2017 17:17:35 +0100 [thread overview]
Message-ID: <f30766d6-d2ac-e28e-d410-d57932c3b01f@vivier.eu> (raw)
In-Reply-To: <20171219151636.5162-1-michael.weiser@gmx.de>
Le 19/12/2017 à 16:16, Michael Weiser a écrit :
> Hello,
>
> below patches add support for big-endian aarch64 to linux-user. Almost
> everything is already in place. The patches just set up the CPU flags as
> required for big-endianess, add a distinction in uname and make sure the
> instructions for the signal trampoline end up in memory little-endian.
> Finally, configure is extended to allow building of a
> aarch64_be-linux-user target.
>
> With this I am able to run individual aarch64_be binaries as well as
> chroot into a full-blown aarch64_be userland using binfmt_misc, running
> and compiling things (Gentoo crossdev/native).
Could you also update scripts/qemu-binfmt-conf.sh for the aarch64_be magic?
Thanks,
Laurent
next prev parent reply other threads:[~2017-12-19 16:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 15:16 [Qemu-devel] [PATCH 0/4] Add aarch64_be-linux-user target Michael Weiser
2017-12-19 15:16 ` [Qemu-devel] [PATCH 1/4] linux-user: Add support for big-endian aarch64 Michael Weiser
2017-12-19 15:16 ` [Qemu-devel] [PATCH 2/4] linux-user: Add separate aarch64_be uname Michael Weiser
2017-12-19 15:16 ` [Qemu-devel] [PATCH 3/4] linux-user: Fix endianess of aarch64 signal trampoline Michael Weiser
2017-12-19 15:16 ` [Qemu-devel] [PATCH 4/4] configure: Add aarch64_be-linux-user target Michael Weiser
2017-12-19 16:17 ` Laurent Vivier [this message]
2017-12-19 20:15 ` [Qemu-devel] [PATCH 0/4] " Michael Weiser
2017-12-19 17:00 ` no-reply
2017-12-20 16:52 ` Richard Henderson
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=f30766d6-d2ac-e28e-d410-d57932c3b01f@vivier.eu \
--to=laurent@vivier.eu \
--cc=michael.weiser@gmx.de \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).