summaryrefslogtreecommitdiffstats
path: root/include/exec
diff options
context:
space:
mode:
authorDavid Gibson2016-02-09 00:28:58 +0100
committerDavid Gibson2016-02-16 23:59:30 +0100
commit715c54071a43ab978dc12b9da22a5016203ed284 (patch)
treee94539962f1fa2894ce2a5bd150a9a2913ead835 /include/exec
parenttarget-ppc: Include missing MMU models for SDR1 in info registers (diff)
downloadqemu-715c54071a43ab978dc12b9da22a5016203ed284.tar.gz
qemu-715c54071a43ab978dc12b9da22a5016203ed284.tar.xz
qemu-715c54071a43ab978dc12b9da22a5016203ed284.zip
pseries: Simplify handling of the hash page table fd
When migrating the 'pseries' machine type with KVM, we use a special fd to access the hash page table stored within KVM. Usually, this fd is opened at the beginning of migration, and kept open until the migration is complete. However, if there is a guest reset during the migration, the fd can become stale and we need to re-open it. At the moment we use an 'htab_fd_stale' flag in sPAPRMachineState to signal this, which is checked in the migration iterators. But that's rather ugly. It's simpler to just close and invalidate the fd on reset, and lazily re-open it in migration if necessary. This patch implements that change. This requires a small addition to the machine state's instance_init, so that htab_fd is initialized to -1 (telling the migration code it needs to open it) instead of 0, which could be a valid fd. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Reviewed-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Diffstat (limited to 'include/exec')
0 files changed, 0 insertions, 0 deletions