All of lore.kernel.org
 help / color / mirror / Atom feed
From: matheus.ferst@eldorado.org.br
To: qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: laurent@vivier.eu, Matheus Ferst <matheus.ferst@eldorado.org.br>,
	richard.henderson@linaro.org, groug@kaod.org,
	david@gibson.dropbear.id.au
Subject: [PATCH 0/4] Fix incorrect accesses to XER
Date: Thu, 14 Oct 2021 19:32:30 -0300	[thread overview]
Message-ID: <20211014223234.127012-1-matheus.ferst@eldorado.org.br> (raw)

From: Matheus Ferst <matheus.ferst@eldorado.org.br>

This patch series fixes some uses of env->xer that were left behind when
SO, OV, and CA bits were separated into other fields of CPUPPCState. At
the time, all of them weren't in target-specific files/directories,
which probably made it harder to track what needed to be changed.
Currently, this still is the case for linux-user/elfload.c. Is there
any particular reason for that? I can try to provide a patch to split
it.

Matheus Ferst (4):
  linux-user/ppc: Fix XER access in save/restore_user_regs
  target/ppc: Fix XER access in gdbstub
  linux-user: Fix XER access in ppc version of elf_core_copy_regs
  target/ppc: Fix XER access in monitor

 linux-user/elfload.c                        |  2 +-
 linux-user/ppc/signal.c                     |  9 +++--
 target/ppc/cpu.c                            |  2 +-
 target/ppc/cpu.h                            |  2 +-
 target/ppc/gdbstub.c                        |  8 ++--
 target/ppc/monitor.c                        |  9 ++++-
 tests/tcg/ppc64/Makefile.target             |  2 +
 tests/tcg/ppc64le/Makefile.target           |  2 +
 tests/tcg/ppc64le/signal_save_restore_xer.c | 42 +++++++++++++++++++++
 9 files changed, 67 insertions(+), 11 deletions(-)
 create mode 100644 tests/tcg/ppc64le/signal_save_restore_xer.c

-- 
2.25.1



             reply	other threads:[~2021-10-14 22:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14 22:32 matheus.ferst [this message]
2021-10-14 22:32 ` [PATCH 1/4] linux-user/ppc: Fix XER access in save/restore_user_regs matheus.ferst
2021-10-14 23:43   ` Richard Henderson
2021-10-15 14:54     ` Matheus K. Ferst
2021-10-15 18:24       ` Richard Henderson
2021-10-15  0:30   ` David Gibson
2021-10-14 22:32 ` [PATCH 2/4] target/ppc: Fix XER access in gdbstub matheus.ferst
2021-10-14 23:43   ` Richard Henderson
2021-10-15  0:31   ` David Gibson
2021-10-14 22:32 ` [PATCH 3/4] linux-user: Fix XER access in ppc version of elf_core_copy_regs matheus.ferst
2021-10-14 23:44   ` Richard Henderson
2021-10-14 22:32 ` [PATCH 4/4] target/ppc: Fix XER access in monitor matheus.ferst
2021-10-14 23:45   ` 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=20211014223234.127012-1-matheus.ferst@eldorado.org.br \
    --to=matheus.ferst@eldorado.org.br \
    --cc=david@gibson.dropbear.id.au \
    --cc=groug@kaod.org \
    --cc=laurent@vivier.eu \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=richard.henderson@linaro.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.