On 05.06.2012, at 03:04, Anthony Liguori wrote: > On 06/05/2012 09:00 AM, Alexander Graf wrote: >> >> On 05.06.2012, at 02:58, Anthony Liguori wrote: >> >>> On 06/05/2012 08:54 AM, Andreas Färber wrote: >>>> Am 05.06.2012 01:33, schrieb q...@buildbot.b1-systems.de: >>>>> The Buildbot has detected a new failure on builder default_ppc while >>>>> building qemu. >>>>> Full details are available at: >>>>> http://buildbot.b1-systems.de/qemu/builders/default_ppc/builds/417 >>>>> >>>>> Buildbot URL: http://buildbot.b1-systems.de/qemu/ >>>>> >>>>> Buildslave for this Build: qemu-ppc.opensuse.org >>>>> >>>>> Build Reason: The Nightly scheduler named 'nightly_default' triggered >>>>> this build >>>>> Build Source Stamp: [branch master] HEAD >>>>> Blamelist: >>>>> >>>>> BUILD FAILED: failed compile >>>> >>>> CC ppc-softmmu/kvm-all.o >>>> /home/build/qemu/default_ppc/build/kvm-all.c:66: error: field 'kroute' >>>> has incomplete type >>>> /home/build/qemu/default_ppc/build/kvm-all.c: In function 'kvm_init': >>>> /home/build/qemu/default_ppc/build/kvm-all.c:1289: error: 'KVMState' has >>>> no member named 'direct_msi' >>>> make[1]: *** [kvm-all.o] Error 1 >>>> make: *** [subdir-ppc-softmmu] Error 2 >>> >>> Aren't GSI and even MSI very x86-centric concepts? Why is this code in >>> kvm-all.c to begin with? >> >> Weren't GSIs a logical APIC map thing? > > I think GSI is an ACPI concept actually.
Sorry, too many acronyms. Yeah, I meant ACPI. Though some map was ACPI and another map was Linux specific. I tend to forget which of the 50 layers between hardware and what you see are actually dictated by whom :). Alex
