qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: deller@kernel.org
To: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Cc: Helge Deller <deller@gmx.de>
Subject: [PULL 0/2] hppa64 fixes
Date: Fri, 17 Nov 2023 21:05:19 +0100	[thread overview]
Message-ID: <20231117200521.417330-1-deller@kernel.org> (raw)

From: Helge Deller <deller@gmx.de>

The following changes since commit 34a5cb6d8434303c170230644b2a7c1d5781d197:

  Merge tag 'pull-tcg-20231114' of https://gitlab.com/rth7680/qemu into staging (2023-11-15 08:05:25 -0500)

are available in the Git repository at:

  https://github.com/hdeller/qemu-hppa.git tags/hppa64-fixes-pull-request

for you to fetch changes up to 2f926bfd5b79e6219ae65a1e530b38f37d62b384:

  disas/hppa: Show hexcode of instruction along with disassembly (2023-11-17 18:36:36 +0100)

----------------------------------------------------------------
HPPA64 fixes for 8.2

The SHRPD patch fixes a real translation bug which then allows to boot
the 64-bit Linux kernels of the Debian-11 and Debian-12 installation CDs.

The second patch adds the instruction byte sequence to the
assembly log. This is not an actual bug fix, but it's important since
it helps a lot when trying to fix qemu translation bugs on hppa.

----------------------------------------------------------------

Helge Deller (2):
  target/hppa: Fix 64-bit SHRPD instruction
  disas/hppa: Show hexcode of instruction along with disassembly

 disas/hppa.c            | 6 +++++-
 target/hppa/translate.c | 4 ++--
 2 files changed, 7 insertions(+), 3 deletions(-)

-- 
2.41.0



             reply	other threads:[~2023-11-17 20:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-17 20:05 deller [this message]
2023-11-17 20:05 ` [PULL 1/2] target/hppa: Fix 64-bit SHRPD instruction deller
2023-11-17 20:05 ` [PULL 2/2] disas/hppa: Show hexcode of instruction along with disassembly deller
2023-11-20 14:39 ` [PULL 0/2] hppa64 fixes Stefan Hajnoczi

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=20231117200521.417330-1-deller@kernel.org \
    --to=deller@kernel.org \
    --cc=deller@gmx.de \
    --cc=qemu-devel@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 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).