All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [PATCH 3/3] semihosting: Restrict to TCG
Date: Thu, 30 May 2024 08:27:45 +0100	[thread overview]
Message-ID: <874jafep3i.fsf@draig.linaro.org> (raw)
In-Reply-To: <CABgObfYmuvMq80Xz0ZBZQiHmKgoiSTVVqio8FmmpttT8rg64kA@mail.gmail.com> (Paolo Bonzini's message of "Thu, 30 May 2024 08:02:57 +0200")

Paolo Bonzini <pbonzini@redhat.com> writes:

> On Wed, May 29, 2024 at 5:56 PM Philippe Mathieu-Daudé
> <philmd@linaro.org> wrote:
>> It is pointless to build semihosting when TCG is not available.
>
> Why? I would have naively assumed that a suitable semihosting API
> could be implemented by KVM. The justification (and thus the commit
> message) needs to be different for each architecture if it's a matter
> of instruction set or insufficient KVM userspace API.

For Arm at least the HLT instruction is an external debug feature and as
such not trappable by KVM.

>
> Paolo
>
>> Signed-off-by: Philippe Mathieu-Daudé <philmd@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
>>

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


  parent reply	other threads:[~2024-05-30  7:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-29 15:55 [PATCH 0/3] semihosting: Restrict to TCG Philippe Mathieu-Daudé
2024-05-29 15:55 ` [PATCH 1/3] target/mips: Restrict semihosting " Philippe Mathieu-Daudé
2024-05-29 15:55 ` [PATCH 2/3] target/riscv: " Philippe Mathieu-Daudé
2024-05-29 15:55 ` [PATCH 3/3] semihosting: Restrict " Philippe Mathieu-Daudé
2024-05-30  6:02   ` Paolo Bonzini
2024-05-30  7:22     ` Philippe Mathieu-Daudé
2024-05-30  7:31       ` Paolo Bonzini
2024-05-30 13:58         ` Philippe Mathieu-Daudé
2024-06-12 13:12           ` Philippe Mathieu-Daudé
2024-06-18 11:33             ` Philippe Mathieu-Daudé
2024-06-18 13:56               ` Alex Bennée
2024-06-18 14:16                 ` Philippe Mathieu-Daudé
2024-06-19  7:49             ` Paolo Bonzini
2024-07-17 10:49               ` Philippe Mathieu-Daudé
2024-05-30  7:27     ` Alex Bennée [this message]
2024-05-29 17:40 ` [PATCH 0/3] " Richard Henderson
2024-05-29 19:11 ` Alex Bennée
2024-05-30  6:03   ` Paolo Bonzini
2024-05-30  7:23     ` Philippe Mathieu-Daudé

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=874jafep3i.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.