On Wed, 4 Nov 2020 at 04:50, Michael S. Tsirkin <m...@redhat.com> wrote: > > Sending v2 since v1 was borken on 32 bit. > > The following changes since commit c7a7a877b716cf14848f1fd5c754d293e2f8d852: > > Merge remote-tracking branch > 'remotes/pmaydell/tags/pull-target-arm-20201102' into staging (2020-11-03 > 10:38:05 +0000) > > are available in the Git repository at: > > git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git tags/for_upstream > > for you to fetch changes up to 5676edd6d984b0696d206faa230c8da15e271044: > > vhost-user-blk-test: fix races by using fd passing (2020-11-03 16:39:06 > -0500) > > ---------------------------------------------------------------- > pc,pci,vhost,virtio: fixes > > Lots of fixes all over the place. > virtio-mem and virtio-iommu patches are kind of fixes but > it seems better to just make them behave sanely than > try to educate users about the limitations ... > > Signed-off-by: Michael S. Tsirkin <m...@redhat.com>
Fails 'make check' on ppc64be and s390x, ie the big-endian hosts: ** ERROR:../../tests/qtest/libqos/virtio.c:228:qvirtio_wait_used_elem: assertion failed: (g_get_monotonic_time() - start_time <= timeout_us) ERROR qtest-i386/qos-test - Bail out! ERROR:../../tests/qtest/libqos/virtio.c:228:qvirtio_wait_used_elem: assertion failed: (g_get_monotonic_time() - start_time <= timeout_us) thanks -- PMM
