qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] buildbot failure in qemu on default_ppc


From: Alexander Graf
Subject: Re: [Qemu-devel] buildbot failure in qemu on default_ppc
Date: Tue, 5 Jun 2012 03:00:31 +0200

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 address@hidden:
>>> 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? Either way, MSI is not exactly 
x86-centric. You can easily do MSI on ppc as well. I'm not sure if the way it's 
implemented and the way we might one day expose it through an in-kernel 
[X|M]PIC will be identical though.


Alex




reply via email to

[Prev in Thread] Current Thread [Next in Thread]