| commit | 9b00ea4906a618756bcd10f09d432780eab87782 | |
| author | David Gibson <david@gibson.dropbear.id.au> | |
| Sun, 7 Apr 2013 19:08:22 +0000 (7 19:08 +0000) | ||
| committer | Alexander Graf <agraf@suse.de> | |
| Fri, 26 Apr 2013 21:02:41 +0000 (26 23:02 +0200) | ||
| tree | 3b26921583351ac16c09af89552aaeffc885545b | treesnapshot (tar.gz zip) |
| parent | e03c902cb617414dae49d77a810f6957ff7affac | commitdiff |
target-ppc: Synchronize VPA state with KVM
For PAPR guests, KVM tracks the various areas registered with the
H_REGISTER_VPA hypercall. For full emulation, of course, these are tracked
within qemu. At present these values are not synchronized. This is a
problem for reset (qemu's reset of the VPA address is not pushed to KVM)
and will also be a problem for savevm / migration.
The kernel now supports accessing the VPA state via the ONE_REG interface,
this patch adds code to qemu to use that interface to keep the qemu and
KVM ideas of the VPA state synchronized.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Alexander Graf <agraf@suse.de>
For PAPR guests, KVM tracks the various areas registered with the
H_REGISTER_VPA hypercall. For full emulation, of course, these are tracked
within qemu. At present these values are not synchronized. This is a
problem for reset (qemu's reset of the VPA address is not pushed to KVM)
and will also be a problem for savevm / migration.
The kernel now supports accessing the VPA state via the ONE_REG interface,
this patch adds code to qemu to use that interface to keep the qemu and
KVM ideas of the VPA state synchronized.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Alexander Graf <agraf@suse.de>
| target-ppc/kvm.c | diffblobblamehistory |