criu/protobuf/pagemap.proto

message pagemap_head {
	required uint32 pages_id	= 1;
}

message pagemap_entry {
	required uint64 vaddr		= 1;
	required uint32 nr_pages	= 2;
	optional bool	in_parent	= 3;
}
mem: Protobuf format for page dumps Since now we drain pages out of parasite, we can invent any format for page dumps. Let is be ... prorobuf one! :) Another thing to keep in mind, is that we're about to use splices and implement iterative migration, so it's better to have actual pages be page-aligned in the image. And -- backward compatibility. That said the new format is: 1. pagemap-... file which contains a header (currently with a ID of the image with pages, see below) and an array of <nr_pages:vaddr> pairs. The first value means "how many pages to take from the file with pages (see below)" and the second -- where in the task address space to put them. Simple. 2. pages-... file which containes only pages one by one (thus aligned as we want). This patch breaks backward compatibility (old images with pages wil be restored and then crash). Need to do it before v0.5 release. Signed-off-by: Pavel Emelyanov <xemul@parallels.com> 2013-03-12 21:00:05 +04:00			`message pagemap_head {`
proto: Align members and numbers We're aligning members and number in protobuf files from the very beginning for readability sake. So fix up newer ones which were not. Also use /* */ comments, not //. Signed-off-by: Cyrill Gorcunov <gorcunov@openvz.org> Signed-off-by: Pavel Emelyanov <xemul@parallels.com> 2014-02-01 12:27:00 +04:00			`required uint32 pages_id = 1;`
mem: Protobuf format for page dumps Since now we drain pages out of parasite, we can invent any format for page dumps. Let is be ... prorobuf one! :) Another thing to keep in mind, is that we're about to use splices and implement iterative migration, so it's better to have actual pages be page-aligned in the image. And -- backward compatibility. That said the new format is: 1. pagemap-... file which contains a header (currently with a ID of the image with pages, see below) and an array of <nr_pages:vaddr> pairs. The first value means "how many pages to take from the file with pages (see below)" and the second -- where in the task address space to put them. Simple. 2. pages-... file which containes only pages one by one (thus aligned as we want). This patch breaks backward compatibility (old images with pages wil be restored and then crash). Need to do it before v0.5 release. Signed-off-by: Pavel Emelyanov <xemul@parallels.com> 2013-03-12 21:00:05 +04:00			`}`

			`message pagemap_entry {`
proto: Align members and numbers We're aligning members and number in protobuf files from the very beginning for readability sake. So fix up newer ones which were not. Also use /* */ comments, not //. Signed-off-by: Cyrill Gorcunov <gorcunov@openvz.org> Signed-off-by: Pavel Emelyanov <xemul@parallels.com> 2014-02-01 12:27:00 +04:00			`required uint64 vaddr = 1;`
			`required uint32 nr_pages = 2;`
			`optional bool in_parent = 3;`
mem: Protobuf format for page dumps Since now we drain pages out of parasite, we can invent any format for page dumps. Let is be ... prorobuf one! :) Another thing to keep in mind, is that we're about to use splices and implement iterative migration, so it's better to have actual pages be page-aligned in the image. And -- backward compatibility. That said the new format is: 1. pagemap-... file which contains a header (currently with a ID of the image with pages, see below) and an array of <nr_pages:vaddr> pairs. The first value means "how many pages to take from the file with pages (see below)" and the second -- where in the task address space to put them. Simple. 2. pages-... file which containes only pages one by one (thus aligned as we want). This patch breaks backward compatibility (old images with pages wil be restored and then crash). Need to do it before v0.5 release. Signed-off-by: Pavel Emelyanov <xemul@parallels.com> 2013-03-12 21:00:05 +04:00			`}`