From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:42734) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SboIm-00070t-72 for qemu-devel@nongnu.org; Tue, 05 Jun 2012 03:35:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SboIk-0004Dn-Da for qemu-devel@nongnu.org; Tue, 05 Jun 2012 03:35:39 -0400 Received: from mout.web.de ([212.227.17.12]:63455) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SboIk-0004Da-3S for qemu-devel@nongnu.org; Tue, 05 Jun 2012 03:35:38 -0400 Message-ID: <4FCDB6C1.4060602@web.de> Date: Tue, 05 Jun 2012 09:35:29 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <20120604233318.4C32E40771@buildbot.b1-systems.de> <4FCD58B7.9080802@suse.de> <4FCD59A1.4030804@codemonkey.ws> In-Reply-To: <4FCD59A1.4030804@codemonkey.ws> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig68C2CB9321D5AA0D2E16680A" Subject: Re: [Qemu-devel] buildbot failure in qemu on default_ppc List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: agraf@suse.de, Avi Kivity , =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= , qemu-devel@nongnu.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig68C2CB9321D5AA0D2E16680A Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 2012-06-05 02:58, Anthony Liguori wrote: > On 06/05/2012 08:54 AM, Andreas F=C3=A4rber 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' h= as >> no member named 'direct_msi' >> make[1]: *** [kvm-all.o] Error 1 >> make: *** [subdir-ppc-softmmu] Error 2 >=20 > Aren't GSI and even MSI very x86-centric concepts? Why is this code i= n > kvm-all.c to begin with? MSI is a PCI thing, and GSI in the context of KVM's in-kernel irqchip is mostly a historic misnomer. It should have been called VIRQ (virtual IRQ), and I'm using this term now wherever possible. Any architecture that will also support in-kernel irqchips with line-based IRQs or irqfd will have to support this concept as well, thus will most probably use the generic code in kvm-all.c. Jan --------------enig68C2CB9321D5AA0D2E16680A Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/NtsYACgkQitSsb3rl5xSbcACglHgE7zVHV5++ZEjQvET8zsFD f1oAnAycRekfwj/LkCdXlNzI0O/vk4xi =C661 -----END PGP SIGNATURE----- --------------enig68C2CB9321D5AA0D2E16680A--