From: Matheus Tavares Bernardino <quic_mathbern@quicinc.com>
To: <qemu-devel@nongnu.org>
Cc: <alex.bennee@linaro.org>, <bcain@quicinc.com>, <f4bug@amsat.org>,
<peter.maydell@linaro.org>, <tsimpson@quicinc.com>
Subject: [PATCH v2 RESEND 0/7] Hexagon: add lldb support
Date: Thu, 20 Apr 2023 09:31:21 -0300 [thread overview]
Message-ID: <cover.1681993775.git.quic_mathbern@quicinc.com> (raw)
This series allows hexagon programs to be debugged under qemu user-mode
through LLDB and qemu's gdbstub. LLDB implements the GDB remote serial
protocol, so most of the necessary changes are in the Hexagon part itself.
However, one fix is needed at the arch-independent side too.
Changes in v2:
- Rebased on current master
- Added Taylor's Reviewed-by at patch 5
v1: https://lore.kernel.org/qemu-devel/cover.1680808943.git.quic_mathbern@quicinc.com/
Brian Cain (3):
gdbstub: add support for the qRegisterInfo query
Hexagon: support qRegisterInfo at gdbstub
Hexagon (gdbstub): fix p3:0 read and write via stub
Matheus Tavares Bernardino (2):
gdbstub: only send stop-reply packets when allowed to
gdbstub: add test for untimely stop-reply packets
Taylor Simpson (2):
Hexagon (gdbstub): add HVX support
Hexagon (linux-user/hexagon): handle breakpoints
gdbstub/internals.h | 5 +
include/hw/core/cpu.h | 4 +
target/hexagon/gdb_qreginfo.h | 124 ++++++++++++++++++
gdbstub/gdbstub.c | 64 +++++++--
gdbstub/softmmu.c | 13 +-
gdbstub/user.c | 17 ++-
linux-user/hexagon/cpu_loop.c | 10 ++
target/hexagon/cpu.c | 3 +
target/hexagon/gdbstub.c | 76 +++++++++++
tests/guest-debug/run-test.py | 16 ++-
.../multiarch/system/Makefile.softmmu-target | 16 ++-
11 files changed, 326 insertions(+), 22 deletions(-)
create mode 100644 target/hexagon/gdb_qreginfo.h
--
2.39.1
next reply other threads:[~2023-04-20 12:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 12:31 Matheus Tavares Bernardino [this message]
2023-04-20 12:31 ` [PATCH v2 RESEND 1/7] gdbstub: only send stop-reply packets when allowed to Matheus Tavares Bernardino
2023-04-20 13:41 ` Alex Bennée
2023-04-21 11:31 ` Matheus Tavares Bernardino
2023-04-20 12:31 ` [PATCH v2 RESEND 2/7] gdbstub: add test for untimely stop-reply packets Matheus Tavares Bernardino
2023-04-20 13:44 ` Alex Bennée
2023-04-20 12:31 ` [PATCH v2 RESEND 3/7] gdbstub: add support for the qRegisterInfo query Matheus Tavares Bernardino
2023-04-20 13:49 ` Alex Bennée
2023-04-21 11:34 ` Matheus Tavares Bernardino
2023-04-21 13:17 ` Alex Bennée
2023-04-20 14:04 ` Philippe Mathieu-Daudé
2023-04-20 14:05 ` Philippe Mathieu-Daudé
2023-04-20 12:31 ` [PATCH v2 RESEND 4/7] Hexagon: support qRegisterInfo at gdbstub Matheus Tavares Bernardino
2023-04-20 14:06 ` Philippe Mathieu-Daudé
2023-04-21 11:40 ` Matheus Tavares Bernardino
2023-04-20 12:31 ` [PATCH v2 RESEND 5/7] Hexagon (gdbstub): fix p3:0 read and write via stub Matheus Tavares Bernardino
2023-04-20 12:31 ` [PATCH v2 RESEND 6/7] Hexagon (gdbstub): add HVX support Matheus Tavares Bernardino
2023-04-20 12:31 ` [PATCH v2 RESEND 7/7] Hexagon (linux-user/hexagon): handle breakpoints Matheus Tavares Bernardino
2023-04-27 13:31 ` 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=cover.1681993775.git.quic_mathbern@quicinc.com \
--to=quic_mathbern@quicinc.com \
--cc=alex.bennee@linaro.org \
--cc=bcain@quicinc.com \
--cc=f4bug@amsat.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=tsimpson@quicinc.com \
/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).