From: Sven Schnelle <svens@stackframe.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: Helge Deller <deller@gmx.de>, qemu-devel@nongnu.org
Subject: Re: [PATCH 0/3] 64 Bit support for hppa gdbstub
Date: Mon, 18 Mar 2024 07:32:29 +0100 [thread overview]
Message-ID: <87sf0ouk1u.fsf@t14.stackframe.org> (raw)
In-Reply-To: <20240228201434.1515893-1-svens@stackframe.org> (Sven Schnelle's message of "Wed, 28 Feb 2024 21:14:30 +0100")
Hi Richard,
Sven Schnelle <svens@stackframe.org> writes:
> Hi List,
>
> this patchset allows to debug the hppa target when running in wide (64 bit)
> mode. gdb needs a small patch to switch to 64 bit mode. I pushed the
> patch to https://github.com/bminor/binutils-gdb/commit/fd8662ec282d688d1f8100b4365823e57516857b
> With this patch gdb will switch to the appropriate mode when connecting
> to qemu/gdbstub.
>
> Sven Schnelle (3):
> Revert "target/hppa: Drop attempted gdbstub support for hppa64"
> target/hppa: add 64 bit support to gdbstub
> target/hppa: mask CR_SAR register writes to 5/6 bit in gdbstub
>
> target/hppa/gdbstub.c | 66 +++++++++++++++++++++++++++++--------------
> 1 file changed, 45 insertions(+), 21 deletions(-)
gentle ping - if i followed correctly only one patch was reviewed so far.
next prev parent reply other threads:[~2024-03-18 6:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 20:14 [PATCH 0/3] 64 Bit support for hppa gdbstub Sven Schnelle
2024-02-28 20:14 ` [PATCH 1/3] Revert "target/hppa: Drop attempted gdbstub support for hppa64" Sven Schnelle
2024-02-28 20:14 ` [PATCH 2/3] target/hppa: add 64 bit support to gdbstub Sven Schnelle
2024-02-28 20:14 ` [PATCH 3/3] target/hppa: mask CR_SAR register writes to 5/6 bit in gdbstub Sven Schnelle
2024-02-29 18:36 ` Richard Henderson
2024-03-18 6:32 ` Sven Schnelle [this message]
2024-03-18 17:09 ` [PATCH 0/3] 64 Bit support for hppa gdbstub Richard Henderson
2024-03-18 17:24 ` Sven Schnelle
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=87sf0ouk1u.fsf@t14.stackframe.org \
--to=svens@stackframe.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).