From: Anthony Liguori <anthony@codemonkey.ws>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel@nongnu.org, "Jan Kiszka" <jan.kiszka@siemens.com>,
"Andreas Färber" <afaerber@suse.de>,
"Avi Kivity" <avi@redhat.com>
Subject: Re: [Qemu-devel] buildbot failure in qemu on default_ppc
Date: Tue, 05 Jun 2012 09:04:39 +0800 [thread overview]
Message-ID: <4FCD5B27.3090108@codemonkey.ws> (raw)
In-Reply-To: <2FF97AB9-AB8C-42FF-8EF4-2B863AA439E6@suse.de>
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 qemu@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.
> Either way, MSI is not exactly x86-centric. You can easily do MSI on ppc as well.
Okay.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2012-06-05 1:04 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 23:33 [Qemu-devel] buildbot failure in qemu on default_ppc qemu
2012-06-05 0:54 ` Andreas Färber
2012-06-05 0:58 ` Anthony Liguori
2012-06-05 1:00 ` Alexander Graf
2012-06-05 1:04 ` Anthony Liguori [this message]
2012-06-05 1:09 ` Alexander Graf
2012-06-05 7:35 ` Jan Kiszka
2012-06-05 7:31 ` [Qemu-devel] [PATCH] kvm: Fix build for non-CAP_IRQ_ROUTING targets Jan Kiszka
2012-06-05 19:03 ` [Qemu-devel] [PATCH v2] " Jan Kiszka
2012-06-05 19:53 ` Ben Collins
2012-06-06 0:24 ` Andreas Färber
2012-06-06 8:41 ` Avi Kivity
2012-06-06 10:31 ` Jan Kiszka
2012-06-06 10:44 ` Avi Kivity
2012-06-06 11:06 ` Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2013-01-04 13:21 [Qemu-devel] buildbot failure in qemu on default_ppc qemu
2013-01-04 13:37 ` Andreas Färber
2013-01-04 13:46 ` Alexander Graf
2013-01-04 14:12 ` Gerd Hoffmann
2013-01-04 14:17 ` Alexander Graf
2012-08-24 0:39 qemu
2012-07-11 0:19 qemu
2012-06-08 23:34 qemu
2012-06-09 1:44 ` Andreas Färber
2012-03-25 0:03 qemu
2012-01-24 0:10 qemu
2012-01-05 0:31 qemu
2012-01-05 0:26 ` Alexander Graf
2011-09-05 23:44 qemu
2011-07-21 23:06 qemu
2011-06-22 23:27 qemu
2011-06-23 6:17 ` Stefan Hajnoczi
2011-06-23 7:46 ` Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FCD5B27.3090108@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).