On 01/08/2016 03:29 AM, Alexey
Kardashevskiy wrote:
On
01/07/2016 05:22 AM, Mark Cave-Ayland wrote:
This is referenced in
cpu_ppc_handle_mmu_fault() and so should be included
in the migration stream.
Signed-off-by: Mark Cave-Ayland
<mark.cave-ayland@ilande.co.uk>
---
š target-ppc/machine.c |ššš 2 +-
š 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target-ppc/machine.c b/target-ppc/machine.c
index 322ce84..cb56423 100644
--- a/target-ppc/machine.c
+++ b/target-ppc/machine.c
@@ -530,7 +530,7 @@ const VMStateDescription vmstate_ppc_cpu = {
ššššššššš /* Internal state */
ššššššššš VMSTATE_UINTTL(env.hflags_nmsr, PowerPCCPU),
-ššššššš /* FIXME: access_type? */
+ššššššš VMSTATE_INT32(env.access_type, PowerPCCPU),
VMSTATE_INT32_V and you need to change access_type's type from
"int" to "int32_t" (or better use "uint8_t" as it is a simple enum
with 3 possible values).
I don't think uint8_t is going to be safe, since vmstate works with
pointers internally and the cast would only migrate the first *byte* of the value (so the highest
byte on BE).
Alex