From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: Anton Johansson <anjo@rev.ng>,
qemu-devel@nongnu.org,
Richard Henderson <richard.henderson@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v2 1/3] target/mips: Restrict semihosting to TCG
Date: Mon, 10 Jun 2024 16:55:31 +0200 [thread overview]
Message-ID: <9bba0404-982d-44cc-9d4b-cf8e7ad9746c@linaro.org> (raw)
In-Reply-To: <877cex16yt.fsf@draig.linaro.org>
On 10/6/24 11:29, Alex Bennée wrote:
> Philippe Mathieu-Daudé <philmd@linaro.org> writes:
>
>> On 7/6/24 13:08, Anton Johansson wrote:
>>> On 30/05/24, Philippe Mathieu-Daudé wrote:
>>>> Semihosting currently uses the TCG probe_access API. To prepare for
>>>> encoding the TCG dependency in Kconfig, do not enable it unless TCG
>>>> is available.
>>>>
>>>> Suggested-by: Paolo Bonzini <pbonzini@redhat.com>
>>>> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>>>> ---
>>>> target/mips/Kconfig | 2 +-
>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>> xtensa and m68k also `select SEMIHOSTING`, were these missed?
>>
>> TCG is the only accelerator they use, so it is kinda implicit,
>> but you are right, I'll update for completeness.
>
> So I'll wait for a v3?
Yes, on the way...
next prev parent reply other threads:[~2024-06-10 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 14:53 [PATCH v2 0/3] semihosting: Restrict to TCG Philippe Mathieu-Daudé
2024-05-30 14:53 ` [PATCH v2 1/3] target/mips: Restrict semihosting " Philippe Mathieu-Daudé
2024-06-07 11:08 ` Anton Johansson via
2024-06-07 13:48 ` Philippe Mathieu-Daudé
2024-06-10 9:29 ` Alex Bennée
2024-06-10 14:55 ` Philippe Mathieu-Daudé [this message]
2024-05-30 14:53 ` [PATCH v2 2/3] target/riscv: " Philippe Mathieu-Daudé
2024-05-30 14:53 ` [PATCH v2 3/3] semihosting: Restrict " Philippe Mathieu-Daudé
2024-06-03 8:27 ` [PATCH v2 0/3] " Philippe Mathieu-Daudé
2024-06-06 12:43 ` Philippe Mathieu-Daudé
2024-06-06 13:42 ` Anton Johansson via
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=9bba0404-982d-44cc-9d4b-cf8e7ad9746c@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=anjo@rev.ng \
--cc=pbonzini@redhat.com \
--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).