From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org
Cc: qemu-riscv@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Anton Johansson" <anjo@rev.ng>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Max Filippov" <jcmvbkbc@gmail.com>,
"Laurent Vivier" <laurent@vivier.eu>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: [PATCH v3 5/5] semihosting: Restrict to TCG
Date: Mon, 10 Jun 2024 16:58:07 +0200 [thread overview]
Message-ID: <20240610145808.2267-6-philmd@linaro.org> (raw)
In-Reply-To: <20240610145808.2267-1-philmd@linaro.org>
Semihosting currently uses the TCG probe_access API.
It is pointless to have it in the binary when TCG isn't.
Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
---
semihosting/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/semihosting/Kconfig b/semihosting/Kconfig
index eaf3a20ef5..fbe6ac87f9 100644
--- a/semihosting/Kconfig
+++ b/semihosting/Kconfig
@@ -1,6 +1,7 @@
config SEMIHOSTING
bool
+ depends on TCG
config ARM_COMPATIBLE_SEMIHOSTING
bool
--
2.41.0
next prev parent reply other threads:[~2024-06-10 14:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 14:58 [PATCH v3 0/5] semihosting: Restrict to TCG Philippe Mathieu-Daudé
2024-06-10 14:58 ` [PATCH v3 1/5] target/m68k: Restrict semihosting " Philippe Mathieu-Daudé
2024-06-10 14:58 ` [PATCH v3 2/5] target/xtensa: " Philippe Mathieu-Daudé
2024-06-10 18:27 ` Max Filippov
2024-06-10 14:58 ` [PATCH v3 3/5] target/mips: " Philippe Mathieu-Daudé
2024-06-10 14:58 ` [PATCH v3 4/5] target/riscv: " Philippe Mathieu-Daudé
2024-06-11 0:17 ` Alistair Francis
2024-06-10 14:58 ` Philippe Mathieu-Daudé [this message]
2024-06-11 10:07 ` [PATCH v3 0/5] semihosting: Restrict " Alex Bennée
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=20240610145808.2267-6-philmd@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=anjo@rev.ng \
--cc=jcmvbkbc@gmail.com \
--cc=laurent@vivier.eu \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@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).