[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC PATCH 8/8] target/i386: Move X86XSaveArea into TCG
From: |
David Edmondson |
Subject: |
Re: [RFC PATCH 8/8] target/i386: Move X86XSaveArea into TCG |
Date: |
Thu, 08 Jul 2021 17:13:57 +0100 |
On Thursday, 2021-07-08 at 08:22:02 -07, Richard Henderson wrote:
> On 7/8/21 12:45 AM, David Edmondson wrote:
>> Actually, that's nonsense. With KVM or HVF we have to use the offsets of
>> the host CPU, as the hardware won't do anything else, irrespective of
>> the general CPU model chosen.
>>
>> To have KVM -> TCG migration work it would be necessary to pass the
>> offsets in the migration stream and have TCG observe them, as you
>> originally said.
>>
>> TCG -> KVM migration would only be possible if TCG was configured to use
>> the same offsets as would later required by KVM (meaning, the host CPU).
>
> And kvm -> kvm migration, with the same general cpu model chosen, but with
> different host
> cpus with different offsets?
>
> It seems like we must migrate then and verify the offsets in that case, so
> that we can
> fail the migration.
Agreed.
I will look into migrating the offsets.
dme.
--
The sound of a barking dog on a loop, a plane rises in the crystal blue.
- [RFC PATCH 3/8] target/i386: Clarify the padding requirements of X86XSaveArea, (continued)
- [RFC PATCH 3/8] target/i386: Clarify the padding requirements of X86XSaveArea, David Edmondson, 2021/07/05
- [RFC PATCH 7/8] target/i386: Populate x86_ext_save_areas offsets using cpuid where possible, David Edmondson, 2021/07/05
- [RFC PATCH 5/8] target/i386: Make x86_ext_save_areas visible outside cpu.c, David Edmondson, 2021/07/05
- [RFC PATCH 6/8] target/i386: Observe XSAVE state area offsets, David Edmondson, 2021/07/05
- [RFC PATCH 8/8] target/i386: Move X86XSaveArea into TCG, David Edmondson, 2021/07/05
Re: [RFC PATCH 0/8] Derive XSAVE state component offsets from CPUID leaf 0xd where possible, Paolo Bonzini, 2021/07/05