From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:59646) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XOYtD-000305-QF for qemu-devel@nongnu.org; Mon, 01 Sep 2014 17:12:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XOYt4-0000Ae-Mb for qemu-devel@nongnu.org; Mon, 01 Sep 2014 17:11:51 -0400 Received: from mail-we0-x236.google.com ([2a00:1450:400c:c03::236]:38572) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XOYt4-0000AY-FP for qemu-devel@nongnu.org; Mon, 01 Sep 2014 17:11:42 -0400 Received: by mail-we0-f182.google.com with SMTP id w62so6044260wes.27 for ; Mon, 01 Sep 2014 14:11:41 -0700 (PDT) Date: Mon, 1 Sep 2014 23:11:37 +0200 From: Marc =?UTF-8?B?TWFyw60=?= Message-ID: <20140901231137.649d7bb8@crunchbang> In-Reply-To: <20140901182734.6de2abc7@crunchbang> References: <1409566080-6313-1-git-send-email-marc.mari.barcelo@gmail.com> <1409566080-6313-6-git-send-email-marc.mari.barcelo@gmail.com> <20140901180909.6d404d39@bahia.local> <20140901182734.6de2abc7@crunchbang> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH v8 5/7] libqos: Added test case for configuration changes in virtio-blk test List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Greg Kurz Cc: Paolo Bonzini , qemu-devel@nongnu.org, Stefan Hajnoczi El Mon, 1 Sep 2014 18:27:34 +0200 Marc Mar=C3=AD escribi=C3=B3: > El Mon, 1 Sep 2014 18:09:09 +0200 > Greg Kurz escribi=C3=B3: > > On Mon, 1 Sep 2014 12:07:58 +0200 > > Marc Mar=C3=AD wrote: > > > Reviewed-by: Stefan Hajnoczi > > > Signed-off-by: Marc Mar=C3=AD > > > --- > >=20 > > Hi Marc, > >=20 > > I gave it a try for various host/target combinations involving ppc64 > > and x86_64. Here is what I get: > >=20 > > | x86_64 | ppc64 | TARGET > > +------------+-------------+-------- > > x86_64 | OK | assert (1) | > > --------+------------+-------------+ > > ppc64 | assert (2) | assert (1) | > > --------+------------+-------------+ > > ppc64le | OK | assert (1) | > > --------+------------+-------------+ > > HOST | > >=20 > > where OK means: > >=20 > > /virtio/blk/pci/basic: OK > > /virtio/blk/pci/indirect: OK > > /virtio/blk/pci/config: OK > > /virtio/blk/pci/msix: OK > > /virtio/blk/pci/idx: OK > >=20 > > and assert (1) is: > >=20 > > tests/virtio-blk-test.c:87:virtio_blk_init: assertion failed: > > (dev !=3D NULL) > >=20 > > and assert (2) is: > >=20 > > tests/virtio-blk-test.c:171:pci_basic: assertion failed (status =3D=3D > > 0): (2 =3D=3D 0) > >=20 > > I will investigate further but the first column in the array ^^ > > seems to indicate that there's some endianness bug. > >=20 > > Cheers. > >=20 > > -- > > Greg >=20 > Hi >=20 > I will also investigate. Just add that with assert (2), status > is 2, which means status is VIRTIO_BLK_S_UNSUPP, which means "request > unsupported by host". So, for some reason, ppc64 host does not support > a simple write request. >=20 > Thanks for your tests > Marc Hi The problem seems to be that it is not implemented. virtio-blk-test is now using pci-pc, that has the addresses 0xcf8 and 0xcfc hardcoded. These addresses are the key-value for PCI space, to search for devices, and I suppose it is specific to i386 and x86_64. I also searched information to see how easy it is to add another architecture and I could not find much information on ppc64, and even less when mixing ppc64 and PCI. Thanks Marc