From a6c5c07990059c94bf50b0422e953af1368353c0 Mon Sep 17 00:00:00 2001
From: Avi Kivity <avi@redhat.com>
Date: Wed, 7 Dec 2011 18:57:41 +0200
Subject: [PATCH] docs: document memory API interaction with migration
Signed-off-by: Avi Kivity <avi@redhat.com>
---
docs/migration.txt | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/docs/migration.txt b/docs/migration.txt
index 4848c1e52d..f3ddd2f1a8 100644
--- a/docs/migration.txt
+++ b/docs/migration.txt
@@ -219,6 +219,18 @@ The functions to do that are inside a vmstate definition, and are called:
Example: You can look at hpet.c, that uses the three function to
massage the state that is transferred.
+If you use memory API functions that update memory layout outside
+initialization (i.e., in response to a guest action), this is a strong
+indication that you need to call these functions in a post_load callback.
+Examples of such memory API functions are:
+
+ - memory_region_add_subregion()
+ - memory_region_del_subregion()
+ - memory_region_set_readonly()
+ - memory_region_set_enabled()
+ - memory_region_set_address()
+ - memory_region_set_alias_offset()
+
=== Subsections ===
The use of version_id allows to be able to migrate from older versions
--
2.30.2