From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-ppc <qemu-ppc@nongnu.org>,
qemu-devel <qemu-devel@nongnu.org>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] mfocrf missing on e500v2
Date: Fri, 6 Mar 2015 17:25:43 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.2.11.1503061724230.15786@eddie.linux-mips.org> (raw)
In-Reply-To: <71EF659E-A1A2-4938-A99B-856168D156B6@suse.de>
On Fri, 6 Mar 2015, Alexander Graf wrote:
> >> And lo and behold, I really couldn't find any reference to mfocrf in the
> >> e500v2 spec.
> >
> > Do real e500 processors trap on this operation as well?
>
> The illegal instruction I posted about above was when running qemu
> *on* e500v2, because TCG emits mfocrf ;).
Ah OK, fair enough! I guess that answers the question.
Maciej
next prev parent reply other threads:[~2015-03-06 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 16:04 [Qemu-devel] mfocrf missing on e500v2 Alexander Graf
2015-03-06 17:20 ` Maciej W. Rozycki
2015-03-06 17:23 ` Alexander Graf
2015-03-06 17:25 ` Maciej W. Rozycki [this message]
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=alpine.LFD.2.11.1503061724230.15786@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=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).