From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Thomas Huth <thuth@redhat.com>, Alexander Graf <agraf@suse.de>,
qemu-ppc@nongnu.org
Cc: qemu-devel@nongnu.org, lvivier@redhat.com, david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [PATCH 0/2] ppc: Fixes for LSWX and LSWI instructions
Date: Fri, 15 Apr 2016 11:20:03 +0100 [thread overview]
Message-ID: <5710C053.4060805@ilande.co.uk> (raw)
In-Reply-To: <1460646893-32622-1-git-send-email-thuth@redhat.com>
On 14/04/16 16:14, Thomas Huth wrote:
> These two patches fix the bad range checks in the LSWI and LSWX
> instructions.
>
> To see the change in behavior for the lswx instruction, you can use the
> "emulator" test from the kvm-unit-tests suite - code can be found here:
>
> https://git.kernel.org/cgit/virt/kvm/kvm-unit-tests.git/tree/powerpc/emulator.c#n95
>
> For testing the lswi instruction, an additional kvm-unit-test can be
> used, see the patch that I've posted here:
>
> https://patchwork.ozlabs.org/patch/610483/
>
>
> Thomas Huth (2):
> ppc: Fix the range check in the LSWI instruction
> ppc: Fix the bad exception NIP value and the range check in LSWX
>
> target-ppc/cpu.h | 10 ++++++++++
> target-ppc/mem_helper.c | 5 +++--
> target-ppc/translate.c | 6 ++----
> 3 files changed, 15 insertions(+), 6 deletions(-)
I see David has already queued these, however I did give them a spin on
my OpenBIOS PPC test images and didn't see any obvious regressions.
ATB,
Mark.
prev parent reply other threads:[~2016-04-15 10:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 15:14 [Qemu-devel] [PATCH 0/2] ppc: Fixes for LSWX and LSWI instructions Thomas Huth
2016-04-14 15:14 ` [Qemu-devel] [PATCH 1/2] ppc: Fix the range check in the LSWI instruction Thomas Huth
2016-04-14 15:14 ` [Qemu-devel] [PATCH 2/2] ppc: Fix the bad exception NIP value and the range check in LSWX Thomas Huth
2016-04-15 2:52 ` [Qemu-devel] [PATCH 0/2] ppc: Fixes for LSWX and LSWI instructions David Gibson
2016-04-15 10:20 ` Mark Cave-Ayland [this message]
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=5710C053.4060805@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=lvivier@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.