From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Laurent Vivier <laurent@vivier.eu>
Cc: "Fredrik Noring" <noring@nocrew.org>,
"Aleksandar Markovic" <amarkovic@wavecomp.com>,
"Aurelien Jarno" <aurelien@aurel32.net>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Jürgen Urban" <JuergenUrban@gmx.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] linux-user/mips: Support the n32 ABI for the R5900
Date: Fri, 9 Nov 2018 14:14:10 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.2.21.1811091403450.27920@eddie.linux-mips.org> (raw)
In-Reply-To: <39b6a168-22ef-21cc-ae2a-0ce1c3dac5a5@vivier.eu>
On Fri, 9 Nov 2018, Laurent Vivier wrote:
> if you have time, o32 & n32 support needs to be reworked.
>
> We have two binaries qemu-mips and qemu-mipsn32 sharing the same ELF
> mask/magic.
>
> As n32 identifies a kernel ABI version, we should have only one binary
> for qemu-mips and qemu-mipsn32 and the ABI version should be identified
> at runtime as it is done for ARM:
>
> ce4defa062 Arm Linux EABI syscall support.
Are you sure? So is the ARM ABI handled with ce4defa062 64-bit?
The o32 ABI is 32-bit (32-bit GPR width) while n32 is 64-bit (64-bit GPR
width). The correspondence between the i386 ABI and the x86-64 x32 ABI is
analogous to these two ABIs.
How are these x86 ABIs handled WRT the user emulation mode; are they
analogous to the ARM ABIs you've mentioned?
> [I think we can use e_flags for that]
The EF_MIPS_ABI2 `e_flags' bit denotes the n32 ABI. The container format
is ELF32 obviously, because addressing is 32-bit with n32.
> I never did the change because I don't know where to find mipsn32
> binaries to test my changes.
I believe MIPS64 Debian is all n32.
Maciej
next prev parent reply other threads:[~2018-11-09 14:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 18:42 [Qemu-devel] [PATCH 0/2] linux-user/mips: Support the n32 ABI for the R5900 Fredrik Noring
2018-11-08 18:43 ` [Qemu-devel] [PATCH 1/2] " Fredrik Noring
2018-11-09 10:34 ` Laurent Vivier
2021-02-14 15:17 ` Philippe Mathieu-Daudé
2021-02-14 15:44 ` Bin Meng
2021-02-14 17:22 ` Laurent Vivier
2018-11-08 18:43 ` [Qemu-devel] [PATCH 2/2] tests/tcg/mips: Test user mode DMULT " Fredrik Noring
2018-11-09 10:55 ` [Qemu-devel] [PATCH 0/2] linux-user/mips: Support the n32 ABI " Laurent Vivier
2018-11-09 14:14 ` Maciej W. Rozycki [this message]
2018-11-09 14:56 ` Laurent Vivier
2018-11-09 16:34 ` Maciej W. Rozycki
2018-11-12 23:56 ` Maciej W. Rozycki
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=alpine.LFD.2.21.1811091403450.27920@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=JuergenUrban@gmx.de \
--cc=amarkovic@wavecomp.com \
--cc=aurelien@aurel32.net \
--cc=f4bug@amsat.org \
--cc=laurent@vivier.eu \
--cc=noring@nocrew.org \
--cc=qemu-devel@nongnu.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).