diff options
author | Alexander Graf <agraf@suse.de> | 2010-02-19 11:00:43 +0100 |
---|---|---|
committer | Avi Kivity <avi@redhat.com> | 2010-04-25 12:35:24 +0300 |
commit | e5c29e926cd29444d76657398801d49119851a56 (patch) | |
tree | 0863e5d85108c3965419ee9eeb68f6925c97faa2 | |
parent | 0564ee8a8611326f28bae2a0455182b458826762 (diff) | |
download | lwn-e5c29e926cd29444d76657398801d49119851a56.tar.gz lwn-e5c29e926cd29444d76657398801d49119851a56.zip |
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>
-rw-r--r-- | arch/powerpc/kvm/book3s.c | 4 |
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: kvmppc_core_queue_program(vcpu, flags); r = RESUME_GUEST; break; + case EMULATE_DO_MMIO: + run->exit_reason = KVM_EXIT_MMIO; + r = RESUME_HOST_NV; + break; default: BUG(); } |