From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Libo Zhou <zhlb29@foxmail.com>,
Aleksandar Markovic <aleksandar.m.mail@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: illegal hardware instruction during MIPS-I ELF linux user emulation
Date: Mon, 23 Sep 2019 16:38:17 +0200 [thread overview]
Message-ID: <c722d11e-e0ff-8a91-d8f3-ee0a31f1df33@redhat.com> (raw)
In-Reply-To: <tencent_5D6D8ED31E83C5675AB8AA3C@qq.com>
Hi Libo,
On 9/23/19 10:15 AM, Libo Zhou wrote:
> Hi all,
>
> I have an binary file generated by a cross compiler. The 'file' command says
>
> $ file test
> test: ELF 32-bit LSB LSB executable, MIPS, MIPS-I version 1 (SYSV), statically linked, with debug_info, not stripped.
If you look at the mips_defs[] array in
target/mips/translate_init.inc.c, the older ISA implemented is MIPS-II:
$ git grep .insn_flags target/mips/translate_init.inc.c
translate_init.inc.c:75: .insn_flags = CPU_MIPS32,
translate_init.inc.c:97: .insn_flags = CPU_MIPS32 | ASE_MIPS16,
translate_init.inc.c:117: .insn_flags = CPU_MIPS32,
translate_init.inc.c:137: .insn_flags = CPU_MIPS32 | ASE_MIPS16,
translate_init.inc.c:158: .insn_flags = CPU_MIPS32R2,
translate_init.inc.c:179: .insn_flags = CPU_MIPS32R2 | ASE_MIPS16,
translate_init.inc.c:201: .insn_flags = CPU_MIPS32R2 | ASE_MIPS16,
translate_init.inc.c:223: .insn_flags = CPU_MIPS32R2 | ASE_MIPS16
| ASE_DSP,
translate_init.inc.c:249: .insn_flags = CPU_MIPS32R2 | ASE_MIPS16,
translate_init.inc.c:297: .insn_flags = CPU_MIPS32R2 | ASE_MIPS16
| ASE_DSP | ASE_MT,
translate_init.inc.c:323: .insn_flags = CPU_MIPS32R2 | ASE_MIPS16
| ASE_DSP | ASE_DSP_R2,
translate_init.inc.c:343: .insn_flags = CPU_MIPS32R2 | ASE_MICROMIPS,
translate_init.inc.c:364: .insn_flags = CPU_MIPS32R2 | ASE_MICROMIPS,
translate_init.inc.c:410: .insn_flags = CPU_MIPS32R5 | ASE_MSA,
translate_init.inc.c:449: .insn_flags = CPU_MIPS32R6 | ASE_MICROMIPS,
translate_init.inc.c:488: .insn_flags = CPU_NANOMIPS32 | ASE_DSP
| ASE_DSP_R2 | ASE_DSP_R3 |
translate_init.inc.c:511: .insn_flags = CPU_MIPS3,
translate_init.inc.c:531: .insn_flags = CPU_VR54XX,
translate_init.inc.c:552: .insn_flags = CPU_MIPS64,
translate_init.inc.c:578: .insn_flags = CPU_MIPS64,
translate_init.inc.c:607: .insn_flags = CPU_MIPS64 | ASE_MIPS3D,
translate_init.inc.c:636: .insn_flags = CPU_MIPS64R2 | ASE_MIPS3D,
translate_init.inc.c:657: .insn_flags = CPU_MIPS64R2,
translate_init.inc.c:681: .insn_flags = CPU_MIPS64R2,
translate_init.inc.c:721: .insn_flags = CPU_MIPS64R6 | ASE_MSA,
translate_init.inc.c:761: .insn_flags = CPU_MIPS64R6 | ASE_MSA,
translate_init.inc.c:781: .insn_flags = CPU_LOONGSON2E,
translate_init.inc.c:801: .insn_flags = CPU_LOONGSON2F,
translate_init.inc.c:830: .insn_flags = CPU_MIPS64R2 | ASE_DSP |
ASE_DSP_R2,
So currently there is no MIPS-I only CPU.
Note that the code got written with MIPS32 in mind, and implementing
MIPS-I requires a considerable amount of change in the codebase.
> When I executed it with
>
> $./qemu-mipsel test
> qemu: uncaught target signal 4 (Illegal instruction) - core dumped
> [1] 11088 illegal hardware instruction (core dumped) ./qemu-mipsel test
You can try ./qemu-mipsel -d in_asm,int test to display debugging
information, you might see which instruction trapped.
IMO it is likely the RFE (Return from Exception) instruction.
Regards,
Phil.
> However, when I use another cross compiler that generates MIPS32 rel2 binaries, it worked fine.
>
> Can anyone tell me what's going wrong?
>
> Cheers,
> Libo Zhou
>
next prev parent reply other threads:[~2019-09-23 14:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 8:15 illegal hardware instruction during MIPS-I ELF linux user emulation Libo Zhou
2019-09-23 12:04 ` Libo Zhou
2019-09-23 12:19 ` illegal " Peter Maydell
2019-09-24 2:10 ` illegal hardware instruction during MIPS-I ELF linux useremulation Libo Zhou
2019-09-24 2:23 ` Libo Zhou
2019-09-23 14:38 ` Philippe Mathieu-Daudé [this message]
2019-09-23 14:42 ` illegal hardware instruction during MIPS-I ELF linux user emulation Peter Maydell
2019-09-23 14:50 ` Philippe Mathieu-Daudé
2019-09-26 14:31 ` illegal hardware instruction during MIPS-I ELF linux useremulation Libo Zhou
2019-09-26 15:46 ` Philippe Mathieu-Daudé
2019-09-27 8:59 ` Libo Zhou
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=c722d11e-e0ff-8a91-d8f3-ee0a31f1df33@redhat.com \
--to=philmd@redhat.com \
--cc=aleksandar.m.mail@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=zhlb29@foxmail.com \
/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).