summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Wood2013-06-12 09:26:54 +0200
committerMichael Tokarev2013-06-12 11:19:10 +0200
commit821696600402e432f6f11ec355efd23f9bc6ce4f (patch)
tree3d4e5365ba74149adfa26da33f31c646af72584c
parentKVM: S390: Add dummy kvm_arch_init_irq_routing() (diff)
downloadqemu-821696600402e432f6f11ec355efd23f9bc6ce4f.tar.gz
qemu-821696600402e432f6f11ec355efd23f9bc6ce4f.tar.xz
qemu-821696600402e432f6f11ec355efd23f9bc6ce4f.zip
KVM: PPC: Add dummy kvm_arch_init_irq_routing()
The common KVM code insists on calling kvm_arch_init_irq_routing() as soon as it sees kernel header support for it (regardless of whether QEMU supports it). Provide a dummy function to satisfy this. Unlike x86, PPC does not have one default irqchip, so there's no common code that we'd stick here. Even if you ignore the routes themselves, which even on x86 are not set up in this function, the initial XICS kernel implementation will not support IRQ routing, so it's best to leave even the general feature flags up to the specific irqchip code. Signed-off-by: Scott Wood <scottwood@freescale.com> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru> Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
-rw-r--r--target-ppc/kvm.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/target-ppc/kvm.c b/target-ppc/kvm.c
index 3ab2946cfb..2bbc3b81dd 100644
--- a/target-ppc/kvm.c
+++ b/target-ppc/kvm.c
@@ -1797,3 +1797,7 @@ int kvm_arch_on_sigbus(int code, void *addr)
{
return 1;
}
+
+void kvm_arch_init_irq_routing(KVMState *s)
+{
+}