[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-ppc] [PATCHv4 0/5] Clean up compatibility mode handling
From: |
Cédric Le Goater |
Subject: |
Re: [Qemu-ppc] [PATCHv4 0/5] Clean up compatibility mode handling |
Date: |
Thu, 1 Jun 2017 13:59:14 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 |
On 06/01/2017 08:52 AM, David Gibson wrote:
> On Wed, May 31, 2017 at 10:58:57AM +0200, Greg Kurz wrote:
>> On Wed, 31 May 2017 12:57:48 +1000
>> David Gibson <address@hidden> wrote:
>>> [...]
>>>> All old non-pseries machine types already complain when started with
>>>> a POWER7 or newer CPU. Providing the extra error message looks weird:
>>>>
>>>> qemu-system-ppc64 -machine ppce500 \
>>>> -cpu POWER7,compat=power6
>>>> qemu-system-ppc64: CPU 'compat' property is deprecated and has no effect;
>>>> use max-cpu-compat machine property instead
>>>> MMU model 983043 not supported by this machine.
>>>>
>>>> but I guess it's better than crashing. :)
>>>
>>> Well, sure POWER7 doesn't make sense for an e500 machine for other
>>> reasons. But POWER7 or POWER8 _would_ make sense for powernv, where
>>> compat= doesn't.
>>>
>>
>> The powernv machine type doesn't even support CPU features at all:
>>
>> chip_typename = g_strdup_printf(TYPE_PNV_CHIP "-%s", machine->cpu_model);
>> if (!object_class_by_name(chip_typename)) {
>> error_report("invalid CPU model '%s' for %s machine",
>> machine->cpu_model, MACHINE_GET_CLASS(machine)->name);
>> exit(1);
>> }
>
> Ah, well, that's another bug, but not one that's in scope for this
> series.
PowerNV is still work in progress. I would not worry about it too much.
C.