On Mon, 1 Sep 2014 18:27:34 +0200 Marc Marí <marc.mari.barc...@gmail.com> wrote:
> El Mon, 1 Sep 2014 18:09:09 +0200 > Greg Kurz <gk...@linux.vnet.ibm.com> escribió: > > On Mon, 1 Sep 2014 12:07:58 +0200 > > Marc Marí <marc.mari.barc...@gmail.com> wrote: > > > Reviewed-by: Stefan Hajnoczi <stefa...@redhat.com> > > > Signed-off-by: Marc Marí <marc.mari.barc...@gmail.com> > > > --- > > > > Hi Marc, > > > > I gave it a try for various host/target combinations involving ppc64 > > and x86_64. Here is what I get: > > > > | x86_64 | ppc64 | TARGET > > +------------+-------------+-------- > > x86_64 | OK | assert (1) | > > --------+------------+-------------+ > > ppc64 | assert (2) | assert (1) | > > --------+------------+-------------+ > > ppc64le | OK | assert (1) | > > --------+------------+-------------+ > > HOST | > > > > where OK means: > > > > /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 > > > > and assert (1) is: > > > > tests/virtio-blk-test.c:87:virtio_blk_init: assertion failed: (dev != > > NULL) > > > > and assert (2) is: > > > > tests/virtio-blk-test.c:171:pci_basic: assertion failed (status == > > 0): (2 == 0) > > > > I will investigate further but the first column in the array ^^ seems > > to indicate that there's some endianness bug. > > > > Cheers. > > > > -- > > Greg > > Hi > > 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. > Hmmm... ppc64 and ppc64el hosts are exactly the same, except for the CPU endianness. And virtio block works very well with ppc64 ! :) -- Greg
