qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: qemu-devel@nongnu.org
Cc: scottwood@freescale.com
Subject: [Qemu-devel] [PATCH 0/3] PPC: E500: Support SPE guest
Date: Tue, 23 Aug 2011 06:55:41 +0200	[thread overview]
Message-ID: <1314075344-20839-1-git-send-email-agraf@suse.de> (raw)

When I bumped into Jason on Linuxcon, we tried out to run the e500 target
on his Windriver build that used SPE and immediately ran into emulation
issues. Fortunately there weren't too many, so here are the patches to get
a guest using SPE instructions working just fine.

Thanks a lot for the debugging session Jason! It really helps when 2 pairs
of eyes look at code :)


Alex

Alexander Graf (3):
  PPC: E500: Add ESR bit definitions
  PPC: E500: Inject SPE exception on invalid SPE access
  PPC: E500: Set ESR values

 target-ppc/cpu.h       |   17 ++++++++++-
 target-ppc/helper.c    |   10 +++++-
 target-ppc/translate.c |   78 ++++++++++++++++++++++++------------------------
 3 files changed, 63 insertions(+), 42 deletions(-)

             reply	other threads:[~2011-08-23  4:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-23  4:55 Alexander Graf [this message]
2011-08-23  4:55 ` [Qemu-devel] [PATCH 1/3] PPC: E500: Add ESR bit definitions Alexander Graf
2011-08-23  4:55   ` [Qemu-devel] [PATCH 2/3] PPC: E500: Inject SPE exception on invalid SPE access Alexander Graf
2011-08-23  4:55     ` [Qemu-devel] [PATCH 3/3] PPC: E500: Set ESR values Alexander Graf
2011-08-23 20:34     ` [Qemu-devel] [PATCH 2/3] PPC: E500: Inject SPE exception on invalid SPE access Edgar E. Iglesias
2011-08-23 17:00 ` [Qemu-devel] [PATCH 0/3] PPC: E500: Support SPE guest Jason Wessel
2011-08-23 20:10   ` Edgar E. Iglesias

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=1314075344-20839-1-git-send-email-agraf@suse.de \
    --to=agraf@suse.de \
    --cc=qemu-devel@nongnu.org \
    --cc=scottwood@freescale.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).