diff options
| author | Peter Maydell <peter.maydell@linaro.org> | 2024-10-03 15:34:01 +0100 |
|---|---|---|
| committer | Michael Tokarev <mjt@tls.msk.ru> | 2024-10-04 18:54:55 +0300 |
| commit | e300f4c11dae9be4cc2f44837fe6e560576cc27f (patch) | |
| tree | 569a1fb7bfb7d8b11caa45633c6f5c87a4b182b6 /python/scripts/vendor.py | |
| parent | db17daf8c43a321f62f8bc46ea0f4a76e16b386f (diff) | |
| download | qemu-e300f4c11dae9be4cc2f44837fe6e560576cc27f.zip qemu-e300f4c11dae9be4cc2f44837fe6e560576cc27f.tar.gz qemu-e300f4c11dae9be4cc2f44837fe6e560576cc27f.tar.bz2 | |
docs/devel: Mention post_load hook restrictions where we document the hook
Accessing another device in a post_load hook is a bad idea, because
the order of device save/restore is not fixed, and so this
cross-device access makes the save/restore non-deterministic.
We previously only flagged up this requirement in the
record-and-replay developer docs; repeat it in the main migration
documentation, where a developer trying to implement a post_load hook
is more likely to see it.
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Reviewed-by: Michael Tokarev <mjt@tls.msk.ru>
Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
Diffstat (limited to 'python/scripts/vendor.py')
0 files changed, 0 insertions, 0 deletions