From: Fabiano Rosas <farosas@suse.de>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [PATCH 03/22] arm: switch boards to "default y"
Date: Tue, 23 Apr 2024 16:06:35 -0300 [thread overview]
Message-ID: <87h6frj3us.fsf@suse.de> (raw)
In-Reply-To: <CABgObfZ-dUiBhjyL04vz8UoaZvkKCO-a+O63TxxgBEzOrCgt_Q@mail.gmail.com>
Paolo Bonzini <pbonzini@redhat.com> writes:
> Il mar 23 apr 2024, 20:12 Philippe Mathieu-Daudé <philmd@linaro.org> ha
> scritto:
>
>> Hi Fabiano,
>>
>> On 23/4/24 20:02, Fabiano Rosas wrote:
>> > Paolo Bonzini <pbonzini@redhat.com> writes:
>> >
>> >> For ARM targets, boards that require TCG are already using "default y".
>> >> Switch ARM_VIRT to the same selection mechanism.
>> >>
>> >> No changes to generated config-devices.mak file.
>> >>
>> >> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> >> ---
>> >> configs/devices/arm-softmmu/default.mak | 3 ++-
>> >> hw/arm/Kconfig | 2 ++
>> >> 2 files changed, 4 insertions(+), 1 deletion(-)
>> >>
>> >> diff --git a/configs/devices/arm-softmmu/default.mak
>> b/configs/devices/arm-softmmu/default.mak
>> >> index c1cfb3bcf75..31f77c20269 100644
>> >> --- a/configs/devices/arm-softmmu/default.mak
>> >> +++ b/configs/devices/arm-softmmu/default.mak
>> >> @@ -5,7 +5,8 @@
>> >> # CONFIG_PCI_DEVICES=n
>> >> # CONFIG_TEST_DEVICES=n
>> >>
>> >> -CONFIG_ARM_VIRT=y
>> >> +# Boards are selected by default, uncomment to keep out of the build.
>> >> +# CONFIG_ARM_VIRT=n
>> >>
>> >> # These are selected by default when TCG is enabled, uncomment them to
>> >> # keep out of the build.
>> >> diff --git a/hw/arm/Kconfig b/hw/arm/Kconfig
>> >> index 893a7bff66b..1e7cd01087f 100644
>> >> --- a/hw/arm/Kconfig
>> >> +++ b/hw/arm/Kconfig
>> >> @@ -1,5 +1,7 @@
>> >> config ARM_VIRT
>> >> bool
>> >> + default y
>> >> + depends on ARM
>> >> imply PCI_DEVICES
>> >
>> > We lose pci.c when building --without-default-devices:
>> >
>> > $ arch
>> > aarch64
>> > $ ../configure --target-list=aarch64-softmmu,arm-softmmu
>> > --disable-linux-user --without-default-devices
>> > $ make
>> > ...
>> > libqemu-aarch64-softmmu.fa.p/target_arm_kvm.c.o: in function
>> `kvm_arch_fixup_msi_route':
>> > ../target/arm/kvm.c:1548: undefined reference to
>> `pci_device_iommu_address_space'
>>
>
> I guess we can add something like
>
> config AARCH64
> select PCI if KVM
Yep, that fixes the build. With defaults disabled the tests are all
kinds of broken, but I guess that's expected. I see issues even in
master.
With the above included:
Tested-by: Fabiano Rosas <farosas@suse.de> # build-only on aarch64
next prev parent reply other threads:[~2024-04-23 19:07 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 13:15 [PATCH 00/22] configs: switch boards to "default y" Paolo Bonzini
2024-04-23 13:15 ` [PATCH 01/22] configs: list "implied" device groups in the default configs Paolo Bonzini
2024-04-23 13:15 ` [PATCH 02/22] alpha: switch boards to "default y" Paolo Bonzini
2024-04-23 13:38 ` Philippe Mathieu-Daudé
2024-04-23 13:15 ` [PATCH 03/22] arm: " Paolo Bonzini
2024-04-23 18:02 ` Fabiano Rosas
2024-04-23 18:12 ` Philippe Mathieu-Daudé
2024-04-23 18:22 ` Fabiano Rosas
2024-04-23 18:31 ` Paolo Bonzini
2024-04-23 19:06 ` Fabiano Rosas [this message]
2024-04-23 13:15 ` [PATCH 04/22] avr: " Paolo Bonzini
2024-04-23 13:29 ` Philippe Mathieu-Daudé
2024-04-23 13:15 ` [PATCH 05/22] cris: " Paolo Bonzini
2024-04-23 13:38 ` Philippe Mathieu-Daudé
2024-04-23 13:15 ` [PATCH 06/22] hppa: " Paolo Bonzini
2024-04-23 13:37 ` Philippe Mathieu-Daudé
2024-04-23 13:15 ` [PATCH 07/22] i386: " Paolo Bonzini
2024-04-23 13:15 ` [PATCH 08/22] loongarch: " Paolo Bonzini
2024-04-23 13:39 ` Philippe Mathieu-Daudé
2024-04-23 13:15 ` [PATCH 09/22] m68k: " Paolo Bonzini
2024-04-23 13:37 ` Philippe Mathieu-Daudé
2024-04-23 13:16 ` [PATCH 10/22] microblaze: " Paolo Bonzini
2024-04-23 13:36 ` Philippe Mathieu-Daudé
2024-04-23 13:16 ` [PATCH 11/22] meson: make target endianneess available to Kconfig Paolo Bonzini
2024-04-23 20:05 ` Fabiano Rosas
2024-04-23 13:16 ` [PATCH 12/22] mips: switch boards to "default y" Paolo Bonzini
2024-04-23 13:16 ` [PATCH 13/22] nios2: " Paolo Bonzini
2024-04-23 13:40 ` Philippe Mathieu-Daudé
2024-04-23 13:16 ` [PATCH 14/22] openrisc: " Paolo Bonzini
2024-04-23 13:39 ` Philippe Mathieu-Daudé
2024-04-23 13:16 ` [PATCH 15/22] ppc: " Paolo Bonzini
2024-04-23 13:16 ` [PATCH 16/22] riscv: " Paolo Bonzini
2024-04-24 0:05 ` Alistair Francis
2024-04-23 13:16 ` [PATCH 17/22] rx: " Paolo Bonzini
2024-04-23 13:30 ` Philippe Mathieu-Daudé
2024-04-23 13:16 ` [PATCH 18/22] s390x: " Paolo Bonzini
2024-04-23 13:16 ` [PATCH 19/22] sh4: " Paolo Bonzini
2024-04-23 13:31 ` Philippe Mathieu-Daudé
2024-04-23 13:16 ` [PATCH 20/22] sparc: " Paolo Bonzini
2024-04-23 13:16 ` [PATCH 21/22] tricore: " Paolo Bonzini
2024-04-23 13:33 ` Philippe Mathieu-Daudé
2024-04-23 13:16 ` [PATCH 22/22] xtensa: " Paolo Bonzini
2024-04-23 13:35 ` Philippe Mathieu-Daudé
2024-04-23 17:57 ` [PATCH 00/22] configs: " Fabiano Rosas
2024-04-23 18:06 ` Paolo Bonzini
2024-05-03 8:15 ` Paolo Bonzini
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=87h6frj3us.fsf@suse.de \
--to=farosas@suse.de \
--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 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).