qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: BALATON Zoltan <balaton@eik.bme.hu>
To: qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: Nicholas Piggin <npiggin@gmail.com>,
	Daniel Henrique Barboza <danielhb413@gmail.com>,
	clg@kaod.org
Subject: [PATCH v5 0/9] Misc clean ups to target/ppc exception handling
Date: Thu, 18 Jan 2024 23:01:42 +0100 (CET)	[thread overview]
Message-ID: <cover.1705614747.git.balaton@eik.bme.hu> (raw)

These are some small clean ups for target/ppc/excp_helper.c trying to
make this code a bit simpler. No functional change is intended. This
series was submitted before but only partially merged due to freeze
and conflicting series os thia was postponed then to avoid conflicts.

v5:
- rebase on master
- keep logging nip pointing to the sc instruction
- add another patch

v4: Rebased on master dropping what was merged

BALATON Zoltan (9):
  target/ppc: Use env_cpu for cpu_abort in excp_helper
  target/ppc: Readability improvements in exception handlers
  target/ppc: Fix gen_sc to use correct nip
  target/ppc: Move patching nip from exception handler to helper_scv
  target/ppc: Simplify syscall exception handlers
  target/ppc: Clean up ifdefs in excp_helper.c, part 1
  target/ppc: Clean up ifdefs in excp_helper.c, part 2
  target/ppc: Clean up ifdefs in excp_helper.c, part 3
  target/ppc: Remove interrupt handler wrapper functions

 target/ppc/cpu.h         |   1 +
 target/ppc/excp_helper.c | 490 +++++++++++++--------------------------
 target/ppc/translate.c   |  16 +-
 3 files changed, 170 insertions(+), 337 deletions(-)

-- 
2.30.9



             reply	other threads:[~2024-01-18 22:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18 22:01 BALATON Zoltan [this message]
2024-01-18 22:01 ` [PATCH v5 1/9] target/ppc: Use env_cpu for cpu_abort in excp_helper BALATON Zoltan
2024-02-21  9:10   ` Harsh Prateek Bora
2024-01-18 22:01 ` [PATCH v5 2/9] target/ppc: Readability improvements in exception handlers BALATON Zoltan
2024-01-18 22:01 ` [PATCH v5 3/9] target/ppc: Fix gen_sc to use correct nip BALATON Zoltan
2024-01-18 22:01 ` [PATCH v5 4/9] target/ppc: Move patching nip from exception handler to helper_scv BALATON Zoltan
2024-01-18 22:01 ` [PATCH v5 5/9] target/ppc: Simplify syscall exception handlers BALATON Zoltan
2024-02-21  9:20   ` Harsh Prateek Bora
2024-02-21  9:42   ` Harsh Prateek Bora
2024-01-18 22:01 ` [PATCH v5 6/9] target/ppc: Clean up ifdefs in excp_helper.c, part 1 BALATON Zoltan
2024-02-22  9:31   ` Harsh Prateek Bora
2024-01-18 22:01 ` [PATCH v5 7/9] target/ppc: Clean up ifdefs in excp_helper.c, part 2 BALATON Zoltan
2024-02-22  9:34   ` Harsh Prateek Bora
2024-01-18 22:01 ` [PATCH v5 8/9] target/ppc: Clean up ifdefs in excp_helper.c, part 3 BALATON Zoltan
2024-02-22  9:38   ` Harsh Prateek Bora
2024-01-18 22:01 ` [PATCH v5 9/9] target/ppc: Remove interrupt handler wrapper functions BALATON Zoltan
2024-02-22 10:05   ` Harsh Prateek Bora
2024-02-22 10:06   ` Harsh Prateek Bora
2024-02-22 11:15     ` BALATON Zoltan
2024-01-30 21:08 ` [PATCH v5 0/9] Misc clean ups to target/ppc exception handling BALATON Zoltan
2024-02-16 13:24   ` BALATON Zoltan

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=cover.1705614747.git.balaton@eik.bme.hu \
    --to=balaton@eik.bme.hu \
    --cc=clg@kaod.org \
    --cc=danielhb413@gmail.com \
    --cc=npiggin@gmail.com \
    --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 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).