|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v8 --for 4.6 COLO 03/25] libxc/migration: Specification update for DIRTY_BITMAP records
On 07/16/2015 01:13 AM, Andrew Cooper wrote: On 15/07/15 10:18, Yang Hongyang wrote: This sounds better, thanks! + +A dirty_bitmap record is used for secondary to send it's dirty bitmap +to primary while doing a checkpoint under COLO. This record only exists +in back channel.This section should purely be a description of the content. i.e. "A DIRTY\_xxx record is used to convey information about dirty memory in the VM. It is an unordered list of PFNs." Ok. + + 0 1 2 3 4 5 6 7 octet + +-------------------------------------------------+ + | pfn[0] | + +-------------------------------------------------+ + ... + +-------------------------------------------------+ + | pfn[C-1] | + +-------------------------------------------------+ + +The count of the pfn is: record->length/sizeof(uint64_t)."The count of pfns is", although I would like to hope that this is obvious from the diagram. Down here, there should be more description of record circumstances, e.g. currently only applicable in the backchannel of a checkpointed stream. Also please put some validation logic for this in tools/python/xen/migration/libxc.py Will do, thank you. ~Andrew . -- Thanks, Yang. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |