[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC PATCH v3 20/28] target/arm: Set cortex-a57 as default cpu for K
From: |
Fabiano Rosas |
Subject: |
Re: [RFC PATCH v3 20/28] target/arm: Set cortex-a57 as default cpu for KVM-only build |
Date: |
Mon, 16 Jan 2023 10:45:33 -0300 |
Richard Henderson <richard.henderson@linaro.org> writes:
> On 1/13/23 06:04, Fabiano Rosas wrote:
>> The cortex-a15 is not present anymore when CONFIG_TCG=n, so use the
>> cortex-a57 as default cpu for KVM.
>>
>> Signed-off-by: Fabiano Rosas <farosas@suse.de>
>
> Ideally there would not be a default at all, requiring the command-line
> option to be used.
We could probably do that now without impact to users, since KVM would
always require a -cpu option due to the current default being
cortex-a15.
>
> Second choice would be "host", since that's the only value that's actually
> usable (except
> for the off-chance that you're actually running on an a57, which is less and
> less likely
> as time moves on).
>
I'll have to go around fixing qtest first, either to add -cpu or to add
-accel kvm, otherwise we get:
The 'host' CPU type can only be used with KVM or HVF
[RFC PATCH v3 22/28] tests/qtest: Restrict bcm2835-dma-test to CONFIG_RASPI, Fabiano Rosas, 2023/01/13
[RFC PATCH v3 23/28] tests/tcg: Do not build/run TCG tests if TCG is disabled, Fabiano Rosas, 2023/01/13
[RFC PATCH v3 24/28] tests/avocado: Skip tests that require a missing accelerator, Fabiano Rosas, 2023/01/13