aboutsummaryrefslogtreecommitdiffstats
path: root/arch/powerpc/kvm/book3s.c
diff options
context:
space:
mode:
authorAlexander Graf <agraf@suse.de>2010-02-19 05:00:43 -0500
committerAvi Kivity <avi@redhat.com>2010-04-25 05:35:24 -0400
commite5c29e926cd29444d76657398801d49119851a56 (patch)
tree0863e5d85108c3965419ee9eeb68f6925c97faa2 /arch/powerpc/kvm/book3s.c
parent0564ee8a8611326f28bae2a0455182b458826762 (diff)
KVM: PPC: Enable program interrupt to do MMIO
When we get a program interrupt we usually don't expect it to perform an MMIO operation. But why not? When we emulate paired singles, we can end up loading or storing to an MMIO address - and the handling of those happens in the program interrupt handler. So let's teach the program interrupt handler how to deal with EMULATE_MMIO. Signed-off-by: Alexander Graf <agraf@suse.de> Signed-off-by: Avi Kivity <avi@redhat.com>
Diffstat (limited to 'arch/powerpc/kvm/book3s.c')
-rw-r--r--arch/powerpc/kvm/book3s.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/arch/powerpc/kvm/book3s.c b/arch/powerpc/kvm/book3s.c
index 38f242a690f7..0446c5a39ae2 100644
--- a/arch/powerpc/kvm/book3s.c
+++ b/arch/powerpc/kvm/book3s.c
@@ -841,6 +841,10 @@ program_interrupt:
841 kvmppc_core_queue_program(vcpu, flags); 841 kvmppc_core_queue_program(vcpu, flags);
842 r = RESUME_GUEST; 842 r = RESUME_GUEST;
843 break; 843 break;
844 case EMULATE_DO_MMIO:
845 run->exit_reason = KVM_EXIT_MMIO;
846 r = RESUME_HOST_NV;
847 break;
844 default: 848 default:
845 BUG(); 849 BUG();
846 } 850 }