Lines Matching refs:of
14 The _domain save image_ is the context of a running domain used for
15 snapshots of a domain or for transferring domains between hosts during
18 There are a number of problems with the format of the domain save
21 * Dependant on toolstack word size. A number of fields within the
50 The image format consists of two main sections:
59 The image header describes the format of the image (version etc.).
66 The main part of the format is a sequence of different _records_.
68 minimum there is a END record marking the end of the records section.
97 includes the version of this specification that the image complies
100 Tools supporting version _V_ of the specification shall always save
108 one or more zero bits within the first 8 octets of the image.
111 regardless of the setting of the endianness bit.
130 version 0x00000002. The version of this specification.
145 The domain header includes general properties of the domain.
169 page_shift Size of a guest page as a power of two.
178 The legacy stream conversion tool writes a `xen_major` version of 0, and sets
179 `xen_minor` to the version of itself.
187 footer. If `body_length` is not a multiple of 8, the body is padded
188 with zeroes to align the end of the record on an 8 octet boundary.
240 body_length Length in octets of the record body.
242 body Content of the record.
244 padding 0 to 7 octets of zeros to pad the whole record to a multiple
245 of 8 octets.
250 unsupported mandatory record must fail. The contents of optional
253 The following sub-sections specify the record body format for each of
261 An end record marks the end of the image, and shall be the final record
274 The bulk of an image consists of many PAGE_DATA records containing the
297 count Number of pages described in this record.
299 pfn An array of count PFNs and their types.
308 page\_data page\_size octets of uncompressed page contents for each
313 to be no page_data in the record if all pfns are of invalid types.
355 [^2]: In the legacy format, this is the list of unmapped PFNs in the
373 pt_levels (ptl) Number of page table levels (either 3 or 4).
399 p2m_pfn Array of PFNs containing the guest's P2M table, for
410 The format of these records are identical. They are all binary blobs
411 of data which are accessed using specific pairs of domctl hypercalls.
446 The content of the Shared Info page.
457 shared_info Contents of the shared info page. This record
536 count The number of parameters contained in this record.
553 An opaque blob provided by and supplied to the higher layers of the
565 data Blob of toolstack-specific data.
587 represent a consistent view of VM state.
595 CHECKPOINT record marks the end of the libxc portion of the stream
600 process another set of records for the next consistent VM state
601 snapshot. This next set of records may be terminated by another
610 dirty memory in the VM. It is an unordered list of PFNs. Currently only
611 applicable in the backchannel of a checkpointed stream. It is only used
623 The count of pfns is: record->length/sizeof(uint64_t).
630 The set of valid records depends on the guest architecture and type. No
631 assumptions should be made about the ordering or interleaving of
659 be present in the following order as each of them depends on information
680 the validity of architectural state in the context.
698 64-bit Bit 31-63 of the p2m_size field 0 (since p2m_size < 2^32^)
705 This assumes the presence of the extended-info chunk which was
732 1. For compatibility with older code, the receving side of a stream should