From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Claudio Fontana" <cfontana@suse.de>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Cc: Laurent Vivier <lvivier@redhat.com>,
Thomas Huth <thuth@redhat.com>,
Roman Bolshakov <r.bolshakov@yadro.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v23 06/17] meson: add target_user_arch
Date: Thu, 25 Feb 2021 12:22:12 +0100 [thread overview]
Message-ID: <c36f4d37-91a0-c0aa-0954-ed2be76d7134@redhat.com> (raw)
In-Reply-To: <20210225104941.15688-7-cfontana@suse.de>
On 2/25/21 11:49 AM, Claudio Fontana wrote:
> the lack of target_user_arch makes it hard to fully leverage the
> build system in order to separate user code from sysemu code.
>
> Provide it, so that we can avoid the proliferation of #ifdef
> in target code.
>
> Signed-off-by: Claudio Fontana <cfontana@suse.de>
> Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
>
> [claudio: added changes for new target hexagon]
Maybe elsewhere this is useful, but not on this patch IMO.
> Signed-off-by: Claudio Fontana <cfontana@suse.de>
> ---
> meson.build | 5 +++++
> target/alpha/meson.build | 3 +++
> target/arm/meson.build | 2 ++
> target/cris/meson.build | 3 +++
> target/hexagon/meson.build | 3 +++
> target/hppa/meson.build | 3 +++
> target/i386/meson.build | 2 ++
> target/m68k/meson.build | 3 +++
> target/microblaze/meson.build | 3 +++
> target/mips/meson.build | 3 +++
> target/nios2/meson.build | 3 +++
> target/openrisc/meson.build | 3 +++
> target/ppc/meson.build | 3 +++
> target/riscv/meson.build | 3 +++
> target/s390x/meson.build | 3 +++
> target/sh4/meson.build | 3 +++
> target/sparc/meson.build | 3 +++
> target/tilegx/meson.build | 3 +++
> target/tricore/meson.build | 3 +++
> target/xtensa/meson.build | 3 +++
> 20 files changed, 60 insertions(+)
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
next prev parent reply other threads:[~2021-02-25 11:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 10:49 [PATCH v23 00/17] i386 cleanup PART 2 Claudio Fontana
2021-02-25 10:49 ` [PATCH v23 01/17] i386: split cpu accelerators from cpu.c, using AccelCPUClass Claudio Fontana
2021-02-25 10:49 ` [PATCH v23 02/17] cpu: call AccelCPUClass::cpu_realizefn in cpu_exec_realizefn Claudio Fontana
2021-02-25 10:49 ` [PATCH v23 03/17] accel: introduce new accessor functions Claudio Fontana
2021-02-25 10:49 ` [PATCH v23 04/17] target/i386: fix host_cpu_adjust_phys_bits error handling Claudio Fontana
2021-02-25 10:49 ` [PATCH v23 05/17] accel-cpu: make cpu_realizefn return a bool Claudio Fontana
2021-02-25 10:49 ` [PATCH v23 06/17] meson: add target_user_arch Claudio Fontana
2021-02-25 11:22 ` Philippe Mathieu-Daudé [this message]
2021-02-25 10:49 ` [PATCH v23 07/17] i386: split off sysemu-only functionality in tcg-cpu Claudio Fontana
2021-02-25 10:49 ` [PATCH v23 08/17] i386: split smm helper (sysemu) Claudio Fontana
2021-02-25 10:49 ` [PATCH v23 09/17] i386: split tcg excp_helper into sysemu and user parts Claudio Fontana
2021-02-25 10:49 ` [PATCH v23 10/17] i386: move TCG btp_helper into sysemu/ Claudio Fontana
2021-02-25 10:49 ` [PATCH v23 11/17] i386: split misc helper user stubs and sysemu part Claudio Fontana
2021-02-25 10:49 ` [PATCH v23 12/17] i386: separate fpu_helper into user and sysemu parts Claudio Fontana
2021-02-25 10:49 ` [PATCH v23 13/17] i386: split svm_helper into sysemu and stub-only user Claudio Fontana
2021-02-25 10:49 ` [PATCH v23 14/17] i386: split seg_helper into user-only and sysemu parts Claudio Fontana
2021-02-25 10:49 ` [PATCH v23 15/17] i386: split off sysemu part of cpu.c Claudio Fontana
2021-02-25 10:49 ` [PATCH v23 16/17] i386: gdbstub: only write CR0/CR2/CR3/EFER for sysemu Claudio Fontana
2021-02-25 10:49 ` [PATCH v23 17/17] i386: make cpu_load_efer sysemu-only Claudio Fontana
2021-02-25 11:15 ` [PATCH v23 00/17] i386 cleanup PART 2 no-reply
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=c36f4d37-91a0-c0aa-0954-ed2be76d7134@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=cfontana@suse.de \
--cc=ehabkost@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=r.bolshakov@yadro.com \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.com \
/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).