Message ID | 20201008185735.29875-8-paul@xen.org (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | domain context infrastructure | expand |
On 08/10/2020 19:57, Paul Durrant wrote: > From: Paul Durrant <pdurrant@amazon.com> > > The STATIC_DATA_END, X86_CPUID_POLICY and X86_MSR_POLICY record types have > sections explaining what they are but their values are not defined. Indeed > their values are defined as "Reserved for future mandatory records." > > Also, the spec revision is adjusted to match the migration stream version > and an END record is added to the description of a 'typical save record for > and x86 HVM guest.' > > Signed-off-by: Paul Durrant <pdurrant@amazon.com> > Fixes: 6f71b5b1506 ("docs/migration Specify migration v3 and STATIC_DATA_END") > Fixes: ddd273d8863 ("docs/migration: Specify X86_{CPUID,MSR}_POLICY records") > Acked-by: Wei Liu <wl@xen.org> I've committed this. I have no idea where these hunks got lost, because I definitely did have them at some point during the mig-v3 work. ~Andrew
diff --git a/docs/specs/libxc-migration-stream.pandoc b/docs/specs/libxc-migration-stream.pandoc index 6b0c49e97a..8aeab3b11b 100644 --- a/docs/specs/libxc-migration-stream.pandoc +++ b/docs/specs/libxc-migration-stream.pandoc @@ -3,7 +3,7 @@ Andrew Cooper <<andrew.cooper3@citrix.com>> Wen Congyang <<wency@cn.fujitsu.com>> Yang Hongyang <<hongyang.yang@easystack.cn>> -% Revision 2 +% Revision 3 Introduction ============ @@ -227,7 +227,13 @@ type 0x00000000: END 0x0000000F: CHECKPOINT_DIRTY_PFN_LIST (Secondary -> Primary) - 0x00000010 - 0x7FFFFFFF: Reserved for future _mandatory_ + 0x00000010: STATIC_DATA_END + + 0x00000011: X86_CPUID_POLICY + + 0x00000012: X86_MSR_POLICY + + 0x00000013 - 0x7FFFFFFF: Reserved for future _mandatory_ records. 0x80000000 - 0xFFFFFFFF: Reserved for future _optional_ @@ -732,6 +738,7 @@ A typical save record for an x86 HVM guest image would look like: * X86_TSC_INFO * HVM_PARAMS * HVM_CONTEXT +* END record HVM_PARAMS must precede HVM_CONTEXT, as certain parameters can affect the validity of architectural state in the context.