Am 16.06.2013 21:25, schrieb Andreas Färber: > Am 12.06.2013 22:32, schrieb Scott Wood: >> Enables support for the in-kernel MPIC that thas been merged into the >> KVM next branch. This includes irqfd/KVM_IRQ_LINE support from Alex >> Graf (along with some other improvements). >> >> Note from Alex regarding kvm_irqchip_create(): >> >> On x86, one would call kvm_irqchip_create() to initialize an >> in-kernel interrupt controller. That function then goes ahead and >> initializes global capability variables as well as the default irq >> routing table. >> >> On ppc, we can't call kvm_irqchip_create() because we can have >> different types of interrupt controllers. So we want to do all the >> things that function would do for us in the in-kernel device init >> handler. >> >> Signed-off-by: Scott Wood <scottw...@freescale.com> [...] >> --- >> default-configs/ppc-softmmu.mak | 1 + >> default-configs/ppc64-softmmu.mak | 1 + > > This breaks KVM-enabled ppcemb-softmmu build with unresolved symbol > kvm_openpic_connect_vcpu() in e500.o. Fix in my patch: > > http://patchwork.ozlabs.org/patch/251731/
This issue brought up an interesting question: Why didn't the buildbots report this build breakage on ppc-next branch? Both of us didn't see any buildbot emails for quite a while - was this disabled for some reason? I didn't find the answer in https://github.com/b1-systems/buildbot/blob/master/qemu-master.cfg but I noticed that it still has Stefan's rather than Michael's trivial tree URL. Looking at http://buildbot.b1-systems.de/qemu/one_line_per_build I see that most builders fail due to configure - which I guess points at lack of compatible libfdt or dtc submodule. Regards, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
