summaryrefslogtreecommitdiffstats
path: root/slirp/ip_input.c
diff options
context:
space:
mode:
authorMichael S. Tsirkin <mst@redhat.com>2013-08-19 17:26:55 +0300
committerMichael S. Tsirkin <mst@redhat.com>2013-08-21 00:18:39 +0300
commit04920fc0faa4760f9c4fc0e73b992b768099be70 (patch)
tree90921644ff0d58e6e165cc439321328e5d771256 /slirp/ip_input.c
parent0851c9f75ccb0baf28f5bf901b9ffe3c91fcf969 (diff)
downloadhqemu-04920fc0faa4760f9c4fc0e73b992b768099be70.zip
hqemu-04920fc0faa4760f9c4fc0e73b992b768099be70.tar.gz
loader: store FW CFG ROM files in RAM
ROM files that are put in FW CFG are copied to guest ram, by BIOS, but they are not backed by RAM so they don't get migrated. Each time we change two bytes in such a ROM this breaks cross-version migration: since we can migrate after BIOS has read the first byte but before it has read the second one, getting an inconsistent state. Future-proof this by creating, for each such ROM, an MR serving as the backing store. This MR is never mapped into guest memory, but it's registered as RAM so it's migrated with the guest. Naturally, this only helps for -M 1.7 and up, older machine types will still have the cross-version migration bug. Luckily the race window for the problem to trigger is very small, which is also likely why we didn't notice the cross-version migration bug in testing yet. Signed-off-by: Michael S. Tsirkin <mst@redhat.com> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Diffstat (limited to 'slirp/ip_input.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud