qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Duarte Silva <duarte.silva@serializing.me>
To: James Hogan <james.hogan@imgtec.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Support for NetLogic XLP Processors
Date: Wed, 25 Mar 2015 14:20:59 +0000	[thread overview]
Message-ID: <13996240.6S33Ckap3f@lczc1207b1zdcs> (raw)
In-Reply-To: <5512B46A.4080208@imgtec.com>

On Wednesday 25 March 2015 13:13:14 James Hogan wrote:
> Hi Duarte,
> 
> On 22/03/15 11:13, Duarte Silva wrote:
> > Hi guys,
> > 
> > I have been struggling to get some binaries compiled for NetLogic XLP
> > processor to run under QEMU. I have tried a bunch of things (most going
> > back and forth) and always get the following error message:
> > 
> > qemu: uncaught target signal 4 (Illegal instruction) - core dumped
> > Illegal instruction
> > 
> > I tried to debug it using GDB but to no avail. Does anybody have ideas?
> > I'm
> > running QEMU 2.2.1.
> 
> It sounds like the program had an instruction that QEMU doesn't
> recognise, or doesn't think should be allowed on the current CPU which
> you've set with -cpu. You might be able to find out what that
> instruction is by putting this on your qemu command line:
> 
>  -singlestep -d in_asm
Hi James,

thanks for the help :) I have tried with all the CPU's available. None of them 
worked, so I just leave it as undefined. It seems the offending instruction is 
"udi4".

(...)
IN: 
0x765d1fa4:  udi4       a0,v0,zero,0x0

OUT: [size=84]
0x606026b0:  mov    -0x4(%r14),%ebp
0x606026b4:  test   %ebp,%ebp
0x606026b6:  jne    0x606026f5
0x606026bc:  mov    $0x765d1fa4,%ebp
0x606026c1:  mov    %ebp,0x80(%r14)
0x606026c8:  mov    %r14,%rdi
0x606026cb:  mov    $0x14,%esi
0x606026d0:  callq  0x600acaa0
0x606026d5:  jmpq   0x606026da
0x606026da:  mov    $0x765d1fa8,%ebp
0x606026df:  mov    %ebp,0x80(%r14)
0x606026e6:  mov    $0x7fe1de9d3bc0,%rax
0x606026f0:  jmpq   0x62561d26
0x606026f5:  mov    $0x7fe1de9d3bc3,%rax
0x606026ff:  jmpq   0x62561d26

do_raise_exception_err: 20 0
qemu: uncaught target signal 4 (Illegal instruction) - core dumped
Illegal instruction

I have found on QEMU code the following definitions for udi4 (on file 
disas/mips.c):

{"udi4", "s,t,d,+1", 0x70000014, 0xfc00003f, WR_d|RD_s|RD_t, 0, I33 },
{"udi4", "s,t,+2",    0x70000014, 0xfc00003f, WR_d|RD_s|RD_t, 0, I33 },
{"udi4", "s,+3",      0x70000014, 0xfc00003f, WR_d|RD_s|RD_t, 0, I33 },
{"udi4", "+4",         0x70000014, 0xfc00003f, WR_d|RD_s|RD_t, 0, I33 },

Does any of these match the above instruction? It seems so no?

Cheers,
Duarte

> 
> that will cause it to only translate one instruction at a time, and to
> dump each one as it is translated. The last one printed will very likely
> to be the one that is causing the problem.
> 
> Cheers
> James

  reply	other threads:[~2015-03-25 14:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-22 11:13 [Qemu-devel] Support for NetLogic XLP Processors Duarte Silva
2015-03-25 11:26 ` Duarte Silva
2015-03-25 13:13 ` James Hogan
2015-03-25 14:20   ` Duarte Silva [this message]
2015-03-25 14:44     ` Leon Alrae
2015-03-25 14:54       ` Leon Alrae
2015-03-25 15:38         ` Duarte Silva
2015-03-25 17:33           ` Leon Alrae
2015-03-25 23:54             ` Duarte Silva
2015-03-26  9:29               ` Leon Alrae
2015-03-26  9:34                 ` James Hogan
2015-03-26  9:54                   ` Duarte Silva

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=13996240.6S33Ckap3f@lczc1207b1zdcs \
    --to=duarte.silva@serializing.me \
    --cc=james.hogan@imgtec.com \
    --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).