From: Fabiano Rosas <farosas@suse.de>
To: qemu-devel@nongnu.org
Cc: qemu-arm@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Claudio Fontana" <cfontana@suse.de>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Alexander Graf" <agraf@csgraf.de>,
"Cornelia Huck" <cohuck@redhat.com>
Subject: [PATCH v9 00/10] target/arm: Allow CONFIG_TCG=n builds
Date: Mon, 13 Mar 2023 12:10:48 -0300 [thread overview]
Message-ID: <20230313151058.19645-1-farosas@suse.de> (raw)
Changes since v8:
- reverted back to keeping -cpu max code for TCG in tcg/cpu64.c;
- pauth: used tcg_enabled instead of CONFIG_TCG in gdbstub.c. However
we still need to keep the ifdef around the function definition in
gdbstub64.c;
- moved all the regression and test fixes after the patches that
enable the --disable-tcg flag;
- tests with --enable-xen --disable-tcg:
Tests now explicitly skip instead of passing.
We cannot do the check at build time because we build the tests only
once for all the QEMU binaries and the native binary will have
support for KVM, thus breaking our !CONFIG_TCG && !CONFIG_KVM
verification.
I also don't think we can have a wrapper because which accelerators
are used is a test-specific information. The test should be able to
specify which accelerators it needs. In other words there will
always be hardcoded "tcg" and "kvm" strings somewhere.
CI run: https://gitlab.com/farosas/qemu/-/pipelines/804459781
v8:
https://lore.kernel.org/r/20230309201434.10831-1-farosas@suse.de
v7 resend:
https://lore.kernel.org/r/20230228192628.26140-1-farosas@suse.de
v7:
https://lore.kernel.org/r/20230223130841.25916-1-farosas@suse.de
v6:
https://lore.kernel.org/r/20230217201150.22032-1-farosas@suse.de
v5 resend:
https://lore.kernel.org/r/20230213202927.28992-1-farosas@suse.de
v5:
https://lore.kernel.org/r/20230120184825.31626-1-farosas@suse.de
v4:
https://lore.kernel.org/r/20230119135424.5417-1-farosas@suse.de
v3:
https://lore.kernel.org/r/20230113140419.4013-1-farosas@suse.de
v2:
https://lore.kernel.org/r/20230109224232.11661-1-farosas@suse.de
v1:
https://lore.kernel.org/r/20230104215835.24692-1-farosas@suse.de
Claudio Fontana (1):
target/arm: move cpu_tcg to tcg/cpu32.c
Fabiano Rosas (8):
target/arm: Move cortex sysregs into a separate file
target/arm: Move 64-bit TCG CPUs into tcg/
target/arm: gdbstub: Guard M-profile code with CONFIG_TCG
target/arm: gdbstub: Guard pauth code with CONFIG_TCG
tests/qtest: Fix tests when no KVM or TCG are present
tests/avocado: Pass parameters to migration test
arm/Kconfig: Always select SEMIHOSTING when TCG is present
arm/Kconfig: Do not build TCG-only boards on a KVM-only build
Philippe Mathieu-Daudé (1):
gitlab-ci: Check building KVM-only aarch64 target
.gitlab-ci.d/crossbuilds.yml | 11 +
.../custom-runners/ubuntu-22.04-aarch64.yml | 4 -
configs/devices/aarch64-softmmu/default.mak | 4 -
configs/devices/arm-softmmu/default.mak | 39 --
hw/arm/Kconfig | 43 +-
hw/arm/virt.c | 6 +-
target/arm/Kconfig | 7 +
target/arm/cortex-regs.c | 69 ++
target/arm/cpregs.h | 6 +
target/arm/cpu64.c | 633 +----------------
target/arm/gdbstub.c | 8 +-
target/arm/gdbstub64.c | 2 +
target/arm/internals.h | 10 +-
target/arm/meson.build | 2 +-
target/arm/{cpu_tcg.c => tcg/cpu32.c} | 72 +-
target/arm/tcg/cpu64.c | 655 ++++++++++++++++++
target/arm/tcg/meson.build | 2 +
tests/avocado/migration.py | 83 ++-
tests/qtest/arm-cpu-features.c | 12 +-
tests/qtest/bios-tables-test.c | 11 +-
tests/qtest/boot-serial-test.c | 5 +
tests/qtest/migration-test.c | 10 +-
tests/qtest/pxe-test.c | 8 +-
tests/qtest/vmgenid-test.c | 9 +-
24 files changed, 949 insertions(+), 762 deletions(-)
create mode 100644 target/arm/cortex-regs.c
rename target/arm/{cpu_tcg.c => tcg/cpu32.c} (93%)
create mode 100644 target/arm/tcg/cpu64.c
--
2.35.3
next reply other threads:[~2023-03-13 15:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 15:10 Fabiano Rosas [this message]
2023-03-13 15:10 ` [PATCH v9 01/10] target/arm: Move cortex sysregs into a separate file Fabiano Rosas
2023-03-13 15:10 ` [PATCH v9 02/10] target/arm: Move 64-bit TCG CPUs into tcg/ Fabiano Rosas
2023-04-11 13:25 ` Peter Maydell
2023-03-13 15:10 ` [PATCH v9 03/10] target/arm: move cpu_tcg to tcg/cpu32.c Fabiano Rosas
2023-03-13 15:10 ` [PATCH v9 04/10] target/arm: gdbstub: Guard M-profile code with CONFIG_TCG Fabiano Rosas
2023-03-13 15:10 ` [PATCH v9 05/10] target/arm: gdbstub: Guard pauth " Fabiano Rosas
2023-03-13 20:08 ` Richard Henderson
2023-03-13 15:10 ` [PATCH v9 06/10] tests/qtest: Fix tests when no KVM or TCG are present Fabiano Rosas
2023-03-13 15:10 ` [PATCH v9 07/10] tests/avocado: Pass parameters to migration test Fabiano Rosas
2023-03-13 15:10 ` [PATCH v9 08/10] arm/Kconfig: Always select SEMIHOSTING when TCG is present Fabiano Rosas
2023-03-13 15:10 ` [PATCH v9 09/10] arm/Kconfig: Do not build TCG-only boards on a KVM-only build Fabiano Rosas
2023-03-13 15:10 ` [PATCH v9 10/10] gitlab-ci: Check building KVM-only aarch64 target Fabiano Rosas
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=20230313151058.19645-1-farosas@suse.de \
--to=farosas@suse.de \
--cc=agraf@csgraf.de \
--cc=alex.bennee@linaro.org \
--cc=cfontana@suse.de \
--cc=cohuck@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--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 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.