From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: Matheus Ferst <matheus.ferst@eldorado.org.br>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: clg@kaod.org, david@gibson.dropbear.id.au, groug@kaod.org,
farosas@linux.ibm.com, laurent@vivier.eu
Subject: Re: [PATCH 0/6] Fix gen_*_exception error codes
Date: Thu, 14 Jul 2022 10:00:01 -0300 [thread overview]
Message-ID: <53ed8d76-ba31-7f01-4f50-be862a2b3e85@gmail.com> (raw)
In-Reply-To: <20220627141104.669152-1-matheus.ferst@eldorado.org.br>
Queued in gitlab.com/danielhb/qemu/tree/ppc-next. Thanks,
Daniel
On 6/27/22 11:10, Matheus Ferst wrote:
> The first patch of this series is the RFC of [1] (hence the r-b in v1).
> Patches 2~4 follow the other problems that Laurent pointed out, and
> patches 5-6 fix similar problems that I found.
>
> [1] https://lists.gnu.org/archive/html/qemu-ppc/2022-01/msg00400.html
>
> Matheus Ferst (6):
> target/ppc: Fix gen_priv_exception error value in mfspr/mtspr
> target/ppc: fix exception error value in slbfee
> target/ppc: remove mfdcrux and mtdcrux
> target/ppc: fix exception error code in helper_{load,store}_dcr
> target/ppc: fix PMU Group A register read/write exceptions
> target/ppc: fix exception error code in spr_write_excp_vector
>
> target/ppc/cpu.h | 6 ++----
> target/ppc/helper.h | 2 +-
> target/ppc/power8-pmu-regs.c.inc | 10 ++++-----
> target/ppc/timebase_helper.c | 6 +++---
> target/ppc/translate.c | 36 ++++++++------------------------
> 5 files changed, 20 insertions(+), 40 deletions(-)
>
prev parent reply other threads:[~2022-07-14 13:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 14:10 [PATCH 0/6] Fix gen_*_exception error codes Matheus Ferst
2022-06-27 14:10 ` [PATCH 1/6] target/ppc: Fix gen_priv_exception error value in mfspr/mtspr Matheus Ferst
2022-06-27 14:11 ` [PATCH 2/6] target/ppc: fix exception error value in slbfee Matheus Ferst
2022-07-13 20:05 ` Daniel Henrique Barboza
2022-06-27 14:11 ` [PATCH 3/6] target/ppc: remove mfdcrux and mtdcrux Matheus Ferst
2022-06-27 17:49 ` Fabiano Rosas
2022-06-27 14:11 ` [PATCH 4/6] target/ppc: fix exception error code in helper_{load, store}_dcr Matheus Ferst
2022-07-13 20:07 ` [PATCH 4/6] target/ppc: fix exception error code in helper_{load,store}_dcr Daniel Henrique Barboza
2022-06-27 14:11 ` [PATCH 5/6] target/ppc: fix PMU Group A register read/write exceptions Matheus Ferst
2022-06-27 18:00 ` Daniel Henrique Barboza
2022-06-27 14:11 ` [PATCH 6/6] target/ppc: fix exception error code in spr_write_excp_vector Matheus Ferst
2022-07-13 20:08 ` Daniel Henrique Barboza
2022-07-14 13:00 ` Daniel Henrique Barboza [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=53ed8d76-ba31-7f01-4f50-be862a2b3e85@gmail.com \
--to=danielhb413@gmail.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=farosas@linux.ibm.com \
--cc=groug@kaod.org \
--cc=laurent@vivier.eu \
--cc=matheus.ferst@eldorado.org.br \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 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.