From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Gustavo Romero" <gustavo.romero@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
qemu-arm@nongnu.org (open list:ARM TCG CPUs)
Subject: [PULL 07/10] gdbstub: Add support for MTE in system mode
Date: Wed, 11 Sep 2024 07:46:42 +0100 [thread overview]
Message-ID: <20240911064645.357592-8-alex.bennee@linaro.org> (raw)
In-Reply-To: <20240911064645.357592-1-alex.bennee@linaro.org>
From: Gustavo Romero <gustavo.romero@linaro.org>
This commit makes handle_q_memtag, handle_q_isaddresstagged, and
handle_Q_memtag stubs build for system mode, allowing all GDB
'memory-tag' subcommands to work with QEMU gdbstub on aarch64 system
mode.
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/620
Signed-off-by: Gustavo Romero <gustavo.romero@linaro.org>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Message-Id: <20240906143316.657436-3-gustavo.romero@linaro.org>
[AJB: add #ifdef CONFIG_TCG guards]
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20240910173900.4154726-8-alex.bennee@linaro.org>
diff --git a/target/arm/gdbstub64.c b/target/arm/gdbstub64.c
index 85a19c14c7..1a4dbec567 100644
--- a/target/arm/gdbstub64.c
+++ b/target/arm/gdbstub64.c
@@ -430,7 +430,9 @@ int aarch64_gdb_set_tag_ctl_reg(CPUState *cs, uint8_t *buf, int reg)
return 0;
#endif
}
+#endif /* CONFIG_USER_ONLY */
+#ifdef CONFIG_TCG
static void handle_q_memtag(GArray *params, void *user_ctx)
{
ARMCPU *cpu = ARM_CPU(user_ctx);
@@ -600,13 +602,13 @@ static const GdbCmdParseEntry cmd_handler_table[NUM_CMDS] = {
.need_cpu_context = true
},
};
-#endif /* CONFIG_USER_ONLY */
+#endif /* CONFIG_TCG */
void aarch64_cpu_register_gdb_commands(ARMCPU *cpu, GString *qsupported,
GPtrArray *qtable, GPtrArray *stable)
{
-#ifdef CONFIG_USER_ONLY
/* MTE */
+#ifdef CONFIG_TCG
if (cpu_isar_feature(aa64_mte, cpu)) {
g_string_append(qsupported, ";memory-tagging+");
--
2.39.2
next prev parent reply other threads:[~2024-09-11 6:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 6:46 [PULL 00/10] testing and gdbstub updates Alex Bennée
2024-09-11 6:46 ` [PULL 01/10] tests/docker: remove debian-armel-cross Alex Bennée
2024-09-11 6:46 ` [PULL 02/10] tests/docker: update debian i686 and mipsel images to bookworm Alex Bennée
2024-09-11 6:46 ` [PULL 03/10] tests/docker: use debian-all-test-cross for mips64el tests Alex Bennée
2024-09-11 6:46 ` [PULL 04/10] docs/devel: fix duplicate line Alex Bennée
2024-09-11 6:46 ` [PULL 05/10] scripts/ci: update the gitlab-runner playbook Alex Bennée
2024-09-11 6:46 ` [PULL 06/10] gdbstub: Use specific MMU index when probing MTE addresses Alex Bennée
2024-09-11 6:46 ` Alex Bennée [this message]
2024-09-11 6:46 ` [PULL 08/10] tests/guest-debug: Support passing arguments to the GDB test script Alex Bennée
2024-09-11 6:46 ` [PULL 09/10] tests/tcg/aarch64: Improve linker script organization Alex Bennée
2024-09-11 6:46 ` [PULL 10/10] tests/tcg/aarch64: Extend MTE gdbstub tests to system mode Alex Bennée
2024-09-11 18:27 ` [PULL 00/10] testing and gdbstub updates Peter Maydell
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=20240911064645.357592-8-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=gustavo.romero@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--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).