qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Richard Henderson <rth@twiddle.net>
Cc: qemu-ppc <qemu-ppc@nongnu.org>, qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] mfocrf missing on e500v2
Date: Fri, 06 Mar 2015 17:04:05 +0100	[thread overview]
Message-ID: <54F9CFF5.4070800@suse.de> (raw)

Hi Richard,

I've finally managed to check out why my e500v2 automated tests fail to
run. Apparently they break because autotest wants to execute target code
and runs into an illegal instruction while doing that:

Program received signal SIGILL, Illegal instruction.
0xb57c84cc in ?? ()
(gdb) x /i $pc
=> 0xb57c84cc:	mfocrf  r0,1

And lo and behold, I really couldn't find any reference to mfocrf in the
e500v2 spec.

Is there any way to disable setcond2 for those chips?


Alex

             reply	other threads:[~2015-03-06 16:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-06 16:04 Alexander Graf [this message]
2015-03-06 17:20 ` [Qemu-devel] mfocrf missing on e500v2 Maciej W. Rozycki
2015-03-06 17:23   ` Alexander Graf
2015-03-06 17:25     ` Maciej W. Rozycki
2015-03-06 19:37 ` 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=54F9CFF5.4070800@suse.de \
    --to=agraf@suse.de \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=rth@twiddle.net \
    /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).