Alex, this is a backport version that fixed under kvmppc_core_emulate_op()'s
XOP_MTDCR and XOP_MFDCR due to emulate_mtdcr() and emulate_mfdcr() are not
implemented in this code base yet. This has been applied and built correctly.
Please ACK/NAK here in order to be committed there.

>From e43a028752fed049e4bd94ef895542f96d79fa74 Mon Sep 17 00:00:00 2001
From: Alexander Graf <[email protected]>
Date: Sat, 6 Oct 2012 03:56:35 +0200
Subject: [PATCH] KVM: PPC: 44x: fix DCR read/write

When remembering the direction of a DCR transaction, we should write
to the same variable that we interpret on later when doing vcpu_run
again.

Signed-off-by: Alexander Graf <[email protected]>
Cc: [email protected]
Signed-off-by: CAI Qian <[email protected]>

diff --git a/arch/powerpc/kvm/44x_emulate.c b/arch/powerpc/kvm/44x_emulate.c
index c8c6157..c39cd0b 100644
--- a/arch/powerpc/kvm/44x_emulate.c
+++ b/arch/powerpc/kvm/44x_emulate.c
@@ -76,6 +76,7 @@ int kvmppc_core_emulate_op(struct kvm_run *run, struct 
kvm_vcpu *vcpu,
                                run->dcr.dcrn = dcrn;
                                run->dcr.data =  0;
                                run->dcr.is_write = 0;
+                               vcpu->arch.dcr_is_write = 0;
                                vcpu->arch.io_gpr = rt;
                                vcpu->arch.dcr_needed = 1;
                                kvmppc_account_exit(vcpu, DCR_EXITS);
@@ -94,6 +95,7 @@ int kvmppc_core_emulate_op(struct kvm_run *run, struct 
kvm_vcpu *vcpu,
                                run->dcr.dcrn = dcrn;
                                run->dcr.data = kvmppc_get_gpr(vcpu, rs);
                                run->dcr.is_write = 1;
+                               vcpu->arch.dcr_is_write = 1;
                                vcpu->arch.dcr_needed = 1;
                                kvmppc_account_exit(vcpu, DCR_EXITS);
                                emulated = EMULATE_DO_DCR;
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to