Hi Peter,
what do you think of the following patch? We messaged yesterday about
cortex-a15 being the default cpu for virt,
this patch would need also changing the default CPU for virt under KVM I would
think.
Or, we could change the virt default cpu to "max"?
Thanks,
Claudio
On 2/5/21 4:19 PM, Andrew Jones wrote:
> On Fri, Feb 05, 2021 at 03:43:44PM +0100, Philippe Mathieu-Daudé wrote:
>> Support for ARMv7 has been dropped in commit 82bf7ae84ce
>> ("target/arm: Remove KVM support for 32-bit Arm hosts").
>> Restrict the 32-bit CPUs to --enable-tcg builds.
>>
>> Signed-off-by: Philippe Mathieu-Daudé <[email protected]>
>> ---
>> hw/arm/virt.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/hw/arm/virt.c b/hw/arm/virt.c
>> index f5e4a6ec914..ab6300650f9 100644
>> --- a/hw/arm/virt.c
>> +++ b/hw/arm/virt.c
>> @@ -197,8 +197,10 @@ static const int a15irqmap[] = {
>> };
>>
>> static const char *valid_cpus[] = {
>> +#ifdef CONFIG_TCG
>> ARM_CPU_TYPE_NAME("cortex-a7"),
>> ARM_CPU_TYPE_NAME("cortex-a15"),
>> +#endif /* CONFIG_TCG */
>> #ifdef TARGET_AARCH64
>> ARM_CPU_TYPE_NAME("cortex-a53"),
>> ARM_CPU_TYPE_NAME("cortex-a57"),
>> --
>> 2.26.2
>>
>
> So this filters the cpus out of KVM only builds, which seems
> reasonable to do. Of course, if the build is for both KVM and
> TCG, then the cpus won't be filtered out and we'll have to rely
> on the runtime checks to error out if one where to try a 32-bit
> cpu with KVM. But that's fine too, so
>
> Reviewed-by: Andrew Jones <[email protected]>
>
> Thanks,
> drew
>
>
