Message ID | 20171219042942.29297-1-david@gibson.dropbear.id.au |
---|---|
Headers | show |
Series | ppc-for-2.12 queue 20171219 | expand |
On 19 December 2017 at 04:29, David Gibson <david@gibson.dropbear.id.au> wrote: > The following changes since commit eaefea537b476cb853e2edbdc68e969ec777e4bb: > > Merge remote-tracking branch 'remotes/mjt/tags/trivial-patches-fetch' into staging (2017-12-18 14:17:42 +0000) > > are available in the Git repository at: > > git://github.com/dgibson/qemu.git tags/ppc-for-2.12-20171219 > > for you to fetch changes up to eec745d4366076dee068750ea80245e1a46e9c13: > > hw/ide: Emulate SiI3112 SATA controller (2017-12-19 15:24:28 +1100) > > ---------------------------------------------------------------- > ppc patch queue 2017-12-19 > > Here's a second batch of patches for qemu-2.12. Highlights are: > > * Optional capabilities for the "pseries" machine. This removes > some places where we were changing guest visible properties based > on host capabilities, which makes life very bad for migration. > * SLOF update > * Significant TCG speedup from Paolo > * Several new devices for embedded platforms > * Some minor cleanups > Migration test hangs on aarch32 host/ppc guest: peter.m+ 3942 0.0 0.0 1452 412 pts/0 S+ Dec19 0:00 | \_ /bin/sh -c QTEST_QEMU_BINARY=ppc64-softmmu/qemu-system-ppc64 QTEST_QEMU_IMG=qemu-img MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} gtester -k --verbose -m=quick tests/spapr-phb-test tests/endianness-test tests/boot-order-test tests/prom-env-test tests/pnv-xscom-test tests/drive_del-test tests/migration-test tests/boot-serial-test tests/rtas-test tests/pxe-test tests/usb-hcd-ohci-test tests/usb-hcd-uhci-test tests/usb-hcd-xhci-test tests/virtio-net-test tests/virtio-balloon-test tests/virtio-blk-test tests/virtio-rng-test tests/virtio-scsi-test tests/virtio-9p-test tests/virtio-serial-test tests/virtio-console-test tests/test-netfilter tests/test-filter-mirror tests/test-filter-redirector tests/display-vga-test tests/numa-test tests/ivshmem-test tests/qmp-test tests/device-introspect-test tests/qom-test tests/test-hmp peter.m+ 3943 0.0 0.0 11984 1828 pts/0 Sl+ Dec19 0:00 | \_ gtester -k --verbose -m=quick tests/spapr-phb-test tests/endianness-test tests/boot-order-test tests/prom-env-test tests/pnv-xscom-test tests/drive_del-test tests/migration-test tests/boot-serial-test tests/rtas-test tests/pxe-test tests/usb-hcd-ohci-test tests/usb-hcd-uhci-test tests/usb-hcd-xhci-test tests/virtio-net-test tests/virtio-balloon-test tests/virtio-blk-test tests/virtio-rng-test tests/virtio-scsi-test tests/virtio-9p-test tests/virtio-serial-test tests/virtio-console-test tests/test-netfilter tests/test-filter-mirror tests/test-filter-redirector tests/display-vga-test tests/numa-test tests/ivshmem-test tests/qmp-test tests/device-introspect-test tests/qom-test tests/test-hmp peter.m+ 4041 99.9 0.0 3460 824 pts/0 R+ Dec19 809:16 | \_ tests/migration-test --quiet --keep-going -m=quick --GTestLogFD=6 peter.m+ 4042 99.9 0.4 607804 72924 pts/0 Sl+ Dec19 809:50 | \_ ppc64-softmmu/qemu-system-ppc64 -qtest unix:/tmp/qtest-4041.sock,nowait -qtest-log /dev/null -qmp unix:/tmp/qtest-4041.qmp,nowait -machine accel=qtest -display none -machine accel=tcg -m 256M -name pcsource,debug-threads=on -serial file:/tmp/migration-test-vxvkIZ/src_serial -drive file=/tmp/migration-test-vxvkIZ/bootsect,if=pflash,format=raw peter.m+ 4046 0.0 0.3 596596 49696 pts/0 Sl+ Dec19 0:01 | \_ ppc64-softmmu/qemu-system-ppc64 -qtest unix:/tmp/qtest-4041.sock,nowait -qtest-log /dev/null -qmp unix:/tmp/qtest-4041.qmp,nowait -machine accel=qtest -display none -machine accel=tcg -m 256M -name pcdest,debug-threads=on -serial file:/tmp/migration-test-vxvkIZ/dest_serial -incoming unix:/tmp/migration-test-vxvkIZ/migsocket Process 4041/4042 are using 100% CPU. $ QTEST_QEMU_BINARY=ppc64-softmmu/qemu-system-ppc64 gtester -k --verbose -m=quick tests/migration-test TEST: tests/migration-test... (pid=5441) /ppc64/migration/postcopy/unix: [hangs] My first guess is that this is a general 32-bit host issue rather than an arm-host specific one; arm just happens to be the only 32-bit system in my test set. thanks -- PMM
On Wed, Dec 20, 2017 at 11:29:36AM +0000, Peter Maydell wrote: > On 19 December 2017 at 04:29, David Gibson <david@gibson.dropbear.id.au> wrote: > > The following changes since commit eaefea537b476cb853e2edbdc68e969ec777e4bb: > > > > Merge remote-tracking branch 'remotes/mjt/tags/trivial-patches-fetch' into staging (2017-12-18 14:17:42 +0000) > > > > are available in the Git repository at: > > > > git://github.com/dgibson/qemu.git tags/ppc-for-2.12-20171219 > > > > for you to fetch changes up to eec745d4366076dee068750ea80245e1a46e9c13: > > > > hw/ide: Emulate SiI3112 SATA controller (2017-12-19 15:24:28 +1100) > > > > ---------------------------------------------------------------- > > ppc patch queue 2017-12-19 > > > > Here's a second batch of patches for qemu-2.12. Highlights are: > > > > * Optional capabilities for the "pseries" machine. This removes > > some places where we were changing guest visible properties based > > on host capabilities, which makes life very bad for migration. > > * SLOF update > > * Significant TCG speedup from Paolo > > * Several new devices for embedded platforms > > * Some minor cleanups > > > > Migration test hangs on aarch32 host/ppc guest: > > peter.m+ 3942 0.0 0.0 1452 412 pts/0 S+ Dec19 0:00 | > \_ /bin/sh -c > QTEST_QEMU_BINARY=ppc64-softmmu/qemu-system-ppc64 > QTEST_QEMU_IMG=qemu-img MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( > ${RANDOM:-0} % 255 + 1))} gtester -k --verbose -m=quick > tests/spapr-phb-test tests/endianness-test tests/boot-order-test > tests/prom-env-test tests/pnv-xscom-test tests/drive_del-test > tests/migration-test tests/boot-serial-test tests/rtas-test > tests/pxe-test tests/usb-hcd-ohci-test tests/usb-hcd-uhci-test > tests/usb-hcd-xhci-test tests/virtio-net-test > tests/virtio-balloon-test tests/virtio-blk-test tests/virtio-rng-test > tests/virtio-scsi-test tests/virtio-9p-test tests/virtio-serial-test > tests/virtio-console-test tests/test-netfilter > tests/test-filter-mirror tests/test-filter-redirector > tests/display-vga-test tests/numa-test tests/ivshmem-test > tests/qmp-test tests/device-introspect-test tests/qom-test > tests/test-hmp > peter.m+ 3943 0.0 0.0 11984 1828 pts/0 Sl+ Dec19 0:00 | > \_ gtester -k --verbose -m=quick > tests/spapr-phb-test tests/endianness-test tests/boot-order-test > tests/prom-env-test tests/pnv-xscom-test tests/drive_del-test > tests/migration-test tests/boot-serial-test tests/rtas-test > tests/pxe-test tests/usb-hcd-ohci-test tests/usb-hcd-uhci-test > tests/usb-hcd-xhci-test tests/virtio-net-test > tests/virtio-balloon-test tests/virtio-blk-test tests/virtio-rng-test > tests/virtio-scsi-test tests/virtio-9p-test tests/virtio-serial-test > tests/virtio-console-test tests/test-netfilter > tests/test-filter-mirror tests/test-filter-redirector > tests/display-vga-test tests/numa-test tests/ivshmem-test > tests/qmp-test tests/device-introspect-test tests/qom-test > tests/test-hmp > peter.m+ 4041 99.9 0.0 3460 824 pts/0 R+ Dec19 809:16 | > \_ tests/migration-test --quiet > --keep-going -m=quick --GTestLogFD=6 > peter.m+ 4042 99.9 0.4 607804 72924 pts/0 Sl+ Dec19 809:50 | > \_ ppc64-softmmu/qemu-system-ppc64 > -qtest unix:/tmp/qtest-4041.sock,nowait -qtest-log /dev/null -qmp > unix:/tmp/qtest-4041.qmp,nowait -machine accel=qtest -display none > -machine accel=tcg -m 256M -name pcsource,debug-threads=on -serial > file:/tmp/migration-test-vxvkIZ/src_serial -drive > file=/tmp/migration-test-vxvkIZ/bootsect,if=pflash,format=raw > peter.m+ 4046 0.0 0.3 596596 49696 pts/0 Sl+ Dec19 0:01 | > \_ ppc64-softmmu/qemu-system-ppc64 > -qtest unix:/tmp/qtest-4041.sock,nowait -qtest-log /dev/null -qmp > unix:/tmp/qtest-4041.qmp,nowait -machine accel=qtest -display none > -machine accel=tcg -m 256M -name pcdest,debug-threads=on -serial > file:/tmp/migration-test-vxvkIZ/dest_serial -incoming > unix:/tmp/migration-test-vxvkIZ/migsocket > > > Process 4041/4042 are using 100% CPU. > > $ QTEST_QEMU_BINARY=ppc64-softmmu/qemu-system-ppc64 gtester -k > --verbose -m=quick tests/migration-test > TEST: tests/migration-test... (pid=5441) > /ppc64/migration/postcopy/unix: > [hangs] > > My first guess is that this is a general 32-bit host issue > rather than an arm-host specific one; arm just happens to > be the only 32-bit system in my test set. Oh :(. I ran make check SPEED=slow in a 32-bit x86 container before sending the pull request, and I just retried it now, so that doesn't appear to be the case. I haven't the foggiest what could be broken in an arm host specific way, though. Nor do I have easy access to an arm system to track it down on.
On Thu, Dec 21, 2017 at 12:45:50AM +1100, David Gibson wrote: > On Wed, Dec 20, 2017 at 11:29:36AM +0000, Peter Maydell wrote: > > On 19 December 2017 at 04:29, David Gibson <david@gibson.dropbear.id.au> wrote: > > > The following changes since commit eaefea537b476cb853e2edbdc68e969ec777e4bb: > > > > > > Merge remote-tracking branch 'remotes/mjt/tags/trivial-patches-fetch' into staging (2017-12-18 14:17:42 +0000) > > > > > > are available in the Git repository at: > > > > > > git://github.com/dgibson/qemu.git tags/ppc-for-2.12-20171219 > > > > > > for you to fetch changes up to eec745d4366076dee068750ea80245e1a46e9c13: > > > > > > hw/ide: Emulate SiI3112 SATA controller (2017-12-19 15:24:28 +1100) > > > > > > ---------------------------------------------------------------- > > > ppc patch queue 2017-12-19 > > > > > > Here's a second batch of patches for qemu-2.12. Highlights are: > > > > > > * Optional capabilities for the "pseries" machine. This removes > > > some places where we were changing guest visible properties based > > > on host capabilities, which makes life very bad for migration. > > > * SLOF update > > > * Significant TCG speedup from Paolo > > > * Several new devices for embedded platforms > > > * Some minor cleanups > > > > > > > Migration test hangs on aarch32 host/ppc guest: > > > > peter.m+ 3942 0.0 0.0 1452 412 pts/0 S+ Dec19 0:00 | > > \_ /bin/sh -c > > QTEST_QEMU_BINARY=ppc64-softmmu/qemu-system-ppc64 > > QTEST_QEMU_IMG=qemu-img MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( > > ${RANDOM:-0} % 255 + 1))} gtester -k --verbose -m=quick > > tests/spapr-phb-test tests/endianness-test tests/boot-order-test > > tests/prom-env-test tests/pnv-xscom-test tests/drive_del-test > > tests/migration-test tests/boot-serial-test tests/rtas-test > > tests/pxe-test tests/usb-hcd-ohci-test tests/usb-hcd-uhci-test > > tests/usb-hcd-xhci-test tests/virtio-net-test > > tests/virtio-balloon-test tests/virtio-blk-test tests/virtio-rng-test > > tests/virtio-scsi-test tests/virtio-9p-test tests/virtio-serial-test > > tests/virtio-console-test tests/test-netfilter > > tests/test-filter-mirror tests/test-filter-redirector > > tests/display-vga-test tests/numa-test tests/ivshmem-test > > tests/qmp-test tests/device-introspect-test tests/qom-test > > tests/test-hmp > > peter.m+ 3943 0.0 0.0 11984 1828 pts/0 Sl+ Dec19 0:00 | > > \_ gtester -k --verbose -m=quick > > tests/spapr-phb-test tests/endianness-test tests/boot-order-test > > tests/prom-env-test tests/pnv-xscom-test tests/drive_del-test > > tests/migration-test tests/boot-serial-test tests/rtas-test > > tests/pxe-test tests/usb-hcd-ohci-test tests/usb-hcd-uhci-test > > tests/usb-hcd-xhci-test tests/virtio-net-test > > tests/virtio-balloon-test tests/virtio-blk-test tests/virtio-rng-test > > tests/virtio-scsi-test tests/virtio-9p-test tests/virtio-serial-test > > tests/virtio-console-test tests/test-netfilter > > tests/test-filter-mirror tests/test-filter-redirector > > tests/display-vga-test tests/numa-test tests/ivshmem-test > > tests/qmp-test tests/device-introspect-test tests/qom-test > > tests/test-hmp > > peter.m+ 4041 99.9 0.0 3460 824 pts/0 R+ Dec19 809:16 | > > \_ tests/migration-test --quiet > > --keep-going -m=quick --GTestLogFD=6 > > peter.m+ 4042 99.9 0.4 607804 72924 pts/0 Sl+ Dec19 809:50 | > > \_ ppc64-softmmu/qemu-system-ppc64 > > -qtest unix:/tmp/qtest-4041.sock,nowait -qtest-log /dev/null -qmp > > unix:/tmp/qtest-4041.qmp,nowait -machine accel=qtest -display none > > -machine accel=tcg -m 256M -name pcsource,debug-threads=on -serial > > file:/tmp/migration-test-vxvkIZ/src_serial -drive > > file=/tmp/migration-test-vxvkIZ/bootsect,if=pflash,format=raw > > peter.m+ 4046 0.0 0.3 596596 49696 pts/0 Sl+ Dec19 0:01 | > > \_ ppc64-softmmu/qemu-system-ppc64 > > -qtest unix:/tmp/qtest-4041.sock,nowait -qtest-log /dev/null -qmp > > unix:/tmp/qtest-4041.qmp,nowait -machine accel=qtest -display none > > -machine accel=tcg -m 256M -name pcdest,debug-threads=on -serial > > file:/tmp/migration-test-vxvkIZ/dest_serial -incoming > > unix:/tmp/migration-test-vxvkIZ/migsocket > > > > > > Process 4041/4042 are using 100% CPU. > > > > $ QTEST_QEMU_BINARY=ppc64-softmmu/qemu-system-ppc64 gtester -k > > --verbose -m=quick tests/migration-test > > TEST: tests/migration-test... (pid=5441) > > /ppc64/migration/postcopy/unix: > > [hangs] > > > > My first guess is that this is a general 32-bit host issue > > rather than an arm-host specific one; arm just happens to > > be the only 32-bit system in my test set. > > Oh :(. I ran make check SPEED=slow in a 32-bit x86 container before > sending the pull request, and I just retried it now, so that doesn't > appear to be the case. > > I haven't the foggiest what could be broken in an arm host specific > way, though. Nor do I have easy access to an arm system to track it > down on. After I sent that I remembered my Raspberry Pi. Unfortunately, after spending most of the day getting it compiled, I wasn't able to reproduce the problem. The migration-test completed just fine with my ppc-for-2.12 tree. I'm not sure where to go from here, I don't even have a guess as to which patch in the series might be causing the problem, since none of them seem likely candidates.
On 21 December 2017 at 08:40, David Gibson <david@gibson.dropbear.id.au> wrote: > On Thu, Dec 21, 2017 at 12:45:50AM +1100, David Gibson wrote: >> Oh :(. I ran make check SPEED=slow in a 32-bit x86 container before >> sending the pull request, and I just retried it now, so that doesn't >> appear to be the case. >> >> I haven't the foggiest what could be broken in an arm host specific >> way, though. Nor do I have easy access to an arm system to track it >> down on. > > After I sent that I remembered my Raspberry Pi. Unfortunately, after > spending most of the day getting it compiled, I wasn't able to > reproduce the problem. The migration-test completed just fine with my > ppc-for-2.12 tree. > > I'm not sure where to go from here, I don't even have a guess as to > which patch in the series might be causing the problem, since none of > them seem likely candidates. I can have another look with the setup that failed, but that won't be until the new year, I'm afraid. thanks -- PMM