|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-unstable test] 25571: regressions - trouble: broken/fail/pass
flight 25571 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/25571/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 11 guest-saverestore.2 fail REGR. vs. 25568 test-amd64-i386-xl-qemut-win7-amd64 3 host-install(3) broken REGR. vs. 25568 Tests which did not succeed, but are not blocking: test-armhf-armhf-xl 10 migrate-support-check fail never pass test-amd64-amd64-xl-pcipt-intel 9 guest-start fail never pass test-amd64-i386-xend-qemut-winxpsp3 17 leak-check/check fail never pass test-amd64-i386-xend-winxpsp3 17 leak-check/check fail never pass test-amd64-amd64-xl-qemuu-win7-amd64 14 guest-stop fail never pass test-amd64-i386-xl-qemut-winxpsp3-vcpus1 14 guest-stop fail never pass test-amd64-i386-xl-winxpsp3-vcpus1 14 guest-stop fail never pass test-amd64-amd64-xl-qemuu-winxpsp3 14 guest-stop fail never pass test-amd64-i386-xl-win7-amd64 14 guest-stop fail never pass test-amd64-amd64-xl-qemut-winxpsp3 14 guest-stop fail never pass test-amd64-amd64-xl-winxpsp3 14 guest-stop fail never pass test-amd64-amd64-xl-qemut-win7-amd64 14 guest-stop fail never pass test-amd64-i386-xl-qemuu-win7-amd64 14 guest-stop fail never pass test-amd64-amd64-xl-win7-amd64 14 guest-stop fail never pass version targeted for testing: xen c0975b715bb89f0e2868e7031fc6b90e9eb7f750 baseline version: xen ca57e4c9b8cb02ac8ea0fb474219163fba12bf6f ------------------------------------------------------------ People who touched revisions under test: Ian Campbell <ian.campbell@xxxxxxxxxx> Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> Julien Grall <julien.grall@xxxxxxxxxx> Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> Tim Deegan <tim@xxxxxxx> ------------------------------------------------------------ jobs: build-amd64-xend pass build-i386-xend pass build-amd64 pass build-armhf pass build-i386 pass build-amd64-oldkern pass build-i386-oldkern pass build-amd64-pvops pass build-armhf-pvops pass build-i386-pvops pass test-amd64-amd64-xl pass test-armhf-armhf-xl pass test-amd64-i386-xl pass test-amd64-i386-rhel6hvm-amd pass test-amd64-i386-qemut-rhel6hvm-amd pass test-amd64-i386-qemuu-rhel6hvm-amd pass test-amd64-i386-freebsd10-amd64 pass test-amd64-amd64-xl-qemut-win7-amd64 fail test-amd64-i386-xl-qemut-win7-amd64 broken test-amd64-amd64-xl-qemuu-win7-amd64 fail test-amd64-i386-xl-qemuu-win7-amd64 fail test-amd64-amd64-xl-win7-amd64 fail test-amd64-i386-xl-win7-amd64 fail test-amd64-i386-xl-credit2 pass test-amd64-i386-freebsd10-i386 pass test-amd64-amd64-xl-pcipt-intel fail test-amd64-i386-rhel6hvm-intel pass test-amd64-i386-qemut-rhel6hvm-intel pass test-amd64-i386-qemuu-rhel6hvm-intel pass test-amd64-i386-xl-multivcpu pass test-amd64-amd64-pair pass test-amd64-i386-pair pass test-amd64-amd64-xl-sedf-pin pass test-amd64-amd64-pv pass test-amd64-i386-pv pass test-amd64-amd64-xl-sedf pass test-amd64-i386-xl-qemut-winxpsp3-vcpus1 fail test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 fail test-amd64-i386-xl-winxpsp3-vcpus1 fail test-amd64-i386-xend-qemut-winxpsp3 fail test-amd64-amd64-xl-qemut-winxpsp3 fail test-amd64-amd64-xl-qemuu-winxpsp3 fail test-amd64-i386-xend-winxpsp3 fail test-amd64-amd64-xl-winxpsp3 fail ------------------------------------------------------------ sg-report-flight on osstest.cam.xci-test.com logs: /home/xc_osstest/logs images: /home/xc_osstest/images Logs, config files, etc. are available at http://www.chiark.greenend.org.uk/~xensrcts/logs Test harness code can be found at http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary Not pushing. ------------------------------------------------------------ commit c0975b715bb89f0e2868e7031fc6b90e9eb7f750 Author: Ian Campbell <ian.campbell@xxxxxxxxxx> Date: Tue Mar 18 15:53:21 2014 +0000 xen: arm: fixup a couple of coding style issues The if in domain.c was only syntactically valid because the macro happened to contain enclosing braces. Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx> Acked-by: Julien Grall <julien.grall@xxxxxxxxxx> commit aef91661e1ef53b1ec156603ca679f1adc7ad97e Author: Ian Campbell <ian.campbell@xxxxxxxxxx> Date: Tue Mar 18 15:53:20 2014 +0000 xen: arm: avoid "PV" terminology Xen on ARM guests are neither PV nor HVM, they are just "guests". Avoid the incorrect use of the term pv in the guest type macros. Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx> Acked-by: Julien Grall <julien.grall@xxxxxxxxxx> commit 8200daed053bc7f3dca4ee5b42d9f84934b998d7 Author: Ian Campbell <ian.campbell@xxxxxxxxxx> Date: Mon Mar 17 17:27:40 2014 +0000 xen: arm: make stage 2 page tables walks inner-shareable The comment was previously incorrect and indicated that these mappings were unshared (00) when in reality the register was set for outer-shareable (01). Clarify ORGN0/IRGN0 in the comments while at it. Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx> Acked-by: Julien Grall <julien.grall@xxxxxxxxxx> commit 652302e12e7f189274eae0193527a039808a524c Author: Ian Campbell <ian.campbell@xxxxxxxxxx> Date: Mon Mar 17 14:53:30 2014 +0000 xen: arm: use more specific barriers for read and write barriers. Note that 32-bit does not provide a load variant of the inner shareable barrier, so that remains a full any-any barrier. Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx> Acked-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> Acked-by: Tim Deegan <tim@xxxxxxx> commit fc62d6285964ebf809864e40d76797ed745523e4 Author: Ian Campbell <ian.campbell@xxxxxxxxxx> Date: Mon Mar 17 14:53:29 2014 +0000 xen: arm: weaken SMP barriers to inner shareable. Since all processors are in the inner-shareable domain and we map everything that way this is sufficient. The non-SMP barriers remain full system. Although in principle they could become outer shareable barriers for some hardware this would require us to know which class a given device is. Given the small number of device drivers in Xen itself its probably not worth worrying over, although maybe someone will benchmark at some point. Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx> Acked-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> Acked-by: Tim Deegan <tim@xxxxxxx> commit 292239f05f6877d36ce373b69846aa0793284711 Author: Ian Campbell <ian.campbell@xxxxxxxxxx> Date: Mon Mar 17 14:53:28 2014 +0000 xen: arm: add scope to dsb and dmb macros Everywhere currently passes "sy"stem, so no actual change. Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx> Acked-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> Acked-by: Tim Deegan <tim@xxxxxxx> commit 49632ebf69e4e24ae24d2a524e91b0cc5e8d5b0e Author: Ian Campbell <ian.campbell@xxxxxxxxxx> Date: Mon Mar 17 14:53:27 2014 +0000 xen: arm: Use dmb for smp barriers The full power of dsb is not required in this context. Also change wmb() to be dsb() directly instead of indirectly via mb(), for clarity. Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx> Acked-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> Acked-by: Tim Deegan <tim@xxxxxxx> commit 7f3002a6878e6695e48b9d6cb1ec3a1fed3cf2ef Author: Ian Campbell <ian.campbell@xxxxxxxxxx> Date: Mon Mar 17 14:53:26 2014 +0000 xen: arm: Use SMP barriers when that is all which is required. SMP barriers can be used when all we care about is synchronising against other processors. Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx> Acked-by: Tim Deegan <tim@xxxxxxx> commit b51602fb39653b712f8d102cd9776d0a09b0ee5d Author: Ian Campbell <ian.campbell@xxxxxxxxxx> Date: Mon Mar 17 14:53:25 2014 +0000 xen: arm: consolidate barrier definitions These are effectively identical on both 32- and 64-bit. The only difference is that they implicit "sy" on 32-bit becomes explicit. Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx> Acked-by: Tim Deegan <tim@xxxxxxx> Acked-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> commit d6bed3ddd7d060299cf6aede0c478890725a56b7 Author: Ian Campbell <ian.campbell@xxxxxxxxxx> Date: Mon Mar 17 14:53:24 2014 +0000 xen: arm: Only upgrade guest barriers to inner shareable. Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx> Acked-by: Tim Deegan <tim@xxxxxxx> Acked-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> commit ec86971a9dd5d677184bde971e227475e2065203 Author: Ian Campbell <ian.campbell@xxxxxxxxxx> Date: Mon Mar 17 14:53:23 2014 +0000 xen: arm: map memory as inner shareable. The inner shareable domain contains all SMP processors, including different clusters (e.g. big.LITTLE). Therefore this is the correct thing to use for Xen memory mappings. The outer shareable domain is for devices on busses which are coherent and barrier-aware (e.g. AMBA4 AXI with ACE). While the system domain is for things behind bridges which are not. One wrinkle is that Normal memory with attributes Inner Non-cacheable, Outer Non-cacheable (which we call BUFFERABLE) must be mapped Outer Shareable on ARM v7. Therefore change the prototype of mfn_to_xen_entry to take the attribute index so we can DTRT. On ARMv8 the sharability is ignored and considered to always be Outer Shareable. Don't adjust the barriers, flushes etc, those remain as they were (which is more than is now required). I'll change those in a later patch. Many thanks to Leif for explaining the difference between Inner- and Outer-Shareable in words of two or less syllables, I hope I've replicated that explanation properly above! Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx> Acked-by: Julien Grall <julien.grall@xxxxxxxxxx> commit fe1a6bc7546d006384157b6b004efdd3b9d283c5 Author: Ian Jackson <ian.jackson@xxxxxxxxxxxxx> Date: Tue Mar 18 13:45:25 2014 +0000 libxc: Fix buffer length for get_suspend_file Declaring a formal parameter to have an array type doesn't result in the parameter actually having an array type. The type is "adjusted" to a pointer. (C99 6.9.1(7), 6.7.5.3.) So the use of sizeof in xc_suspend.c:get_suspend_file was wrong. Instead, use the #define. Also get rid of the array size, as it is misleading. Newer versions of gcc warn about the erroneous code: xc_suspend.c:39:25: error: argument to 'sizeof' in 'snprintf' call is the same expression as the destination; did you mean to provide an explicit length? [-Werror=sizeof-pointer-memaccess] Reported-By: Julien Grall <julien.grall@xxxxxxxxxx> Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> CC: Ian Campbell <ian.campbell@xxxxxxxxxx> CC: Julien Grall <julien.grall@xxxxxxxxxx> -- v2: Actually change the declaration of buf. (qemu changes not included) _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |