From: Claudio Fontana <cfontana@suse.de>
To: qemu-devel@nongnu.org
Subject: Re: [PATCH 0/2] semihosting: Move it out of hw/
Date: Tue, 2 Mar 2021 15:46:08 +0100 [thread overview]
Message-ID: <0cec0b74-cac0-d35d-eaaa-3ce96507a922@suse.de> (raw)
In-Reply-To: <463befd2-c384-553b-9a78-bb033d92638e@amsat.org>
Hi Philippe,
On 3/2/21 3:10 PM, Philippe Mathieu-Daudé wrote:
> Cc'ing Claudio.
>
> On 2/26/21 2:13 PM, Philippe Mathieu-Daudé wrote:
>> In order to reduce CONFIG_USER_ONLY uses in hw/, move
>> semihosting out of it, being a generic feature.
I have nothing against it, just what does this buy us?
Maybe I am just missing the point..
Ciao,
Claudio
>>
>> Philippe Mathieu-Daudé (2):
>> semihosting: Move include/hw/semihosting/ -> include/semihosting/
>> semihosting: Move hw/semihosting/ -> semihosting/
>>
>> meson.build | 1 +
>> include/{hw => }/semihosting/console.h | 0
>> include/{hw => }/semihosting/semihost.h | 0
>> {hw/semihosting => semihosting}/common-semi.h | 0
>> gdbstub.c | 2 +-
>> hw/mips/malta.c | 2 +-
>> linux-user/aarch64/cpu_loop.c | 2 +-
>> linux-user/arm/cpu_loop.c | 2 +-
>> linux-user/riscv/cpu_loop.c | 2 +-
>> linux-user/semihost.c | 2 +-
>> {hw/semihosting => semihosting}/arm-compat-semi.c | 6 +++---
>> {hw/semihosting => semihosting}/config.c | 2 +-
>> {hw/semihosting => semihosting}/console.c | 4 ++--
>> softmmu/vl.c | 2 +-
>> stubs/semihost.c | 2 +-
>> target/arm/helper.c | 4 ++--
>> target/arm/m_helper.c | 4 ++--
>> target/arm/translate-a64.c | 2 +-
>> target/arm/translate.c | 2 +-
>> target/lm32/helper.c | 2 +-
>> target/m68k/op_helper.c | 2 +-
>> target/mips/cpu.c | 2 +-
>> target/mips/mips-semi.c | 4 ++--
>> target/mips/translate.c | 2 +-
>> target/nios2/helper.c | 2 +-
>> target/riscv/cpu_helper.c | 2 +-
>> target/unicore32/helper.c | 2 +-
>> target/xtensa/translate.c | 2 +-
>> target/xtensa/xtensa-semi.c | 2 +-
>> Kconfig | 1 +
>> MAINTAINERS | 4 ++--
>> hw/Kconfig | 1 -
>> hw/meson.build | 1 -
>> {hw/semihosting => semihosting}/Kconfig | 0
>> {hw/semihosting => semihosting}/meson.build | 0
>> 35 files changed, 35 insertions(+), 35 deletions(-)
>> rename include/{hw => }/semihosting/console.h (100%)
>> rename include/{hw => }/semihosting/semihost.h (100%)
>> rename {hw/semihosting => semihosting}/common-semi.h (100%)
>> rename {hw/semihosting => semihosting}/arm-compat-semi.c (99%)
>> rename {hw/semihosting => semihosting}/config.c (99%)
>> rename {hw/semihosting => semihosting}/console.c (98%)
>> rename {hw/semihosting => semihosting}/Kconfig (100%)
>> rename {hw/semihosting => semihosting}/meson.build (100%)
>>
>
>
next prev parent reply other threads:[~2021-03-02 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 13:13 [PATCH 0/2] semihosting: Move it out of hw/ Philippe Mathieu-Daudé
2021-02-26 13:13 ` [PATCH 1/2] semihosting: Move include/hw/semihosting/ -> include/semihosting/ Philippe Mathieu-Daudé
2021-02-26 13:13 ` [PATCH 2/2] semihosting: Move hw/semihosting/ -> semihosting/ Philippe Mathieu-Daudé
2021-03-02 14:10 ` [PATCH 0/2] semihosting: Move it out of hw/ Philippe Mathieu-Daudé
2021-03-02 14:46 ` Claudio Fontana [this message]
2021-03-05 10:13 ` 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=0cec0b74-cac0-d35d-eaaa-3ce96507a922@suse.de \
--to=cfontana@suse.de \
--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 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).