[PATCH 03/65] hw/arm/Kconfig: select ARM_GICV5 for ARM_VIRT board

Peter Maydell posted 65 patches 1 month, 2 weeks ago
Maintainers: Peter Maydell <peter.maydell@linaro.org>, Pierrick Bouvier <pierrick.bouvier@linaro.org>, Paolo Bonzini <pbonzini@redhat.com>, "Daniel P. Berrangé" <berrange@redhat.com>, Eduardo Habkost <eduardo@habkost.net>, "Marc-André Lureau" <marcandre.lureau@redhat.com>, "Philippe Mathieu-Daudé" <philmd@linaro.org>
There is a newer version of this series
[PATCH 03/65] hw/arm/Kconfig: select ARM_GICV5 for ARM_VIRT board
Posted by Peter Maydell 1 month, 2 weeks ago
When building the Arm "virt" board, pull in the GICv5.

We haven't added support for creating or wiring up the GICv5 in that
board yet, but adding it to the Kconfig early means that the GICv5
code will be compiled and so we can have more confidence that the
individual commits building it up are correct (or at least compile).

Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
---
 hw/arm/Kconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/hw/arm/Kconfig b/hw/arm/Kconfig
index c66c452737..91a15040a4 100644
--- a/hw/arm/Kconfig
+++ b/hw/arm/Kconfig
@@ -10,6 +10,7 @@ config ARM_VIRT
     imply NVDIMM
     imply IOMMUFD
     select ARM_GIC
+    select ARM_GICV5
     select ACPI
     select ARM_SMMUV3
     select GPIO_KEY
-- 
2.43.0
Re: [PATCH 03/65] hw/arm/Kconfig: select ARM_GICV5 for ARM_VIRT board
Posted by Jonathan Cameron via qemu development 1 month ago
On Mon, 23 Feb 2026 17:01:10 +0000
Peter Maydell <peter.maydell@linaro.org> wrote:

> When building the Arm "virt" board, pull in the GICv5.
> 
> We haven't added support for creating or wiring up the GICv5 in that
> board yet, but adding it to the Kconfig early means that the GICv5
> code will be compiled and so we can have more confidence that the
> individual commits building it up are correct (or at least compile).

Good.  I much prefer this approach to people only enabling build
at the end.

> 
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com>