[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-arm] [RFC v2 PATCH] hw/arm/virt: makes virt a default machine type
From: |
Wainer dos Santos Moschetta |
Subject: |
[Qemu-arm] [RFC v2 PATCH] hw/arm/virt: makes virt a default machine type |
Date: |
Thu, 20 Jun 2019 18:23:14 -0400 |
Peter, Cleber,
Re-sending this email because I forgot to copy the mailing listing.
Sorry. Original message below.
==
Hi Peter et al.,
I came across this when running the acceptance tests in an aarch64 host.
The arch-independent tests fail because, in general, they don't set a
machine type. In order to avoid treating arm targets as special cases
on avocado_qemu framework I prefered to attempt to promote virt as
default for ARM emulation. Moreover since it represents a generic hardware
and its used is broaden advised [1], I found it the right choice.
Maybe that topic was discussed already but I didn't find any reference on
either the mailing list and git logs. It is also true
that I am an ignorant on ARM platform, thus I might be missing
something. Those explain why I send this patch as RFC.
[1] https://wiki.qemu.org/Documentation/Platforms/ARM
Thanks,
Wainer
-- >8 --
Currently none arm target has a default machine type, unlike
others as x86_64 and ppc64. The 'virt' (alias) type represents a
generic ARM hardware, so let's specify it the default machine for
ARM emulation.
Signed-off-by: Wainer dos Santos Moschetta <address@hidden>
---
hw/arm/virt.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/hw/arm/virt.c b/hw/arm/virt.c
index 431e2900fd..2f8aa2bfb7 100644
--- a/hw/arm/virt.c
+++ b/hw/arm/virt.c
@@ -74,6 +74,7 @@
mc->desc = "QEMU " # major "." # minor " ARM Virtual Machine"; \
if (latest) { \
mc->alias = "virt"; \
+ mc->is_default = 1; \
} \
} \
static const TypeInfo machvirt_##major##_##minor##_info = { \
--
2.18.1
- [Qemu-arm] [RFC v2 PATCH] hw/arm/virt: makes virt a default machine type,
Wainer dos Santos Moschetta <=