Difference between revisions of "Memory dumping and restoring"

Revision as of 21:10, 14 May 2013

How it works now

Dumping

Currently memory dumping depends on 3 big technologies:

/proc/pid/map_files/ directory with links is used to determine
- which file is mapped
- shared memory "identifier" to detect the sharing
proc pagemap file says which pages are to be dumped and which are not (to be fixed as well)
Ptrace SEIZE is used to dump the memory contents

Restoring

This one depends only on the /proc/pid/map_files/ to restore the shmem regions -- tasks just open some other's link and map it to create shmem region. The pages restoration just writes page data "in place".

Problems

Non linear mappings

Currently we don't support non-linear mappings (fail dump if present)

Revision as of 19:10, 21 October 2012 (edit) Xemul (talk \| contribs) (→‎Dumping) ← Older edit		Revision as of 21:10, 14 May 2013 (edit) (undo) Xemul (talk \| contribs) (Categorize) Newer edit →
Line 20:		Line 20:

	Currently we don't support non-linear mappings (fail dump if present)		Currently we don't support non-linear mappings (fail dump if present)
		+
		+	[[Category:Under the hood]]