[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-ppc] [RFC PATCH] target-ppc: enable migration within the same

From: Alexey Kardashevskiy
Subject: Re: [Qemu-ppc] [RFC PATCH] target-ppc: enable migration within the same CPU family
Date: Fri, 11 Apr 2014 01:11:10 +1000
User-agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0

On 04/04/2014 11:28 PM, Alexander Graf wrote:
> On 04/04/2014 07:17 AM, Alexey Kardashevskiy wrote:
>> On 03/24/2014 04:28 PM, Alexey Kardashevskiy wrote:
>>> Currently only migration fails if CPU version is different even a bit.
>>> For example, migration from POWER7 v2.0 to POWER7 v2.1 fails because of
>>> that. Since there is no difference between CPU versions which could
>>> affect migration stream, we can safely enable it.
>>> This adds a helper to find the closest POWERPC family class (i.e. first
>>> abstract class in hierarchy).
>>> This replaces VMSTATE_UINTTL_EQUAL statement with a custom handler which
>>> checks if the source and destination CPUs belong to the same family and
>>> fails if they are not.
>>> This adds a PVR reset to the default value as it will be overwritten
>>> by VMSTATE_UINTTL_ARRAY(env.spr, PowerPCCPU, 1024).
>>> Since the actual migration format is not changed by this patch,
>>> @version_id of vmstate_ppc_cpu does not have to be changed either.
>>> Signed-off-by: Bharata B Rao <address@hidden>
>>> Signed-off-by: Alexey Kardashevskiy <address@hidden>
>> Ping?
> Can't we just always allow migration to succeed? It's a problem of the tool
> stack above if it allows migration to an incompatible host, no?

After very convincing mail from Peter Maydell, this is the only solution,
correct? If so, I'll make a patch then.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]