|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [xen-unstable-smoke test] 121348: regressions - FAIL
flight 121348 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/121348/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-libvirt 6 libvirt-build fail REGR. vs. 121346 Tests which did not succeed, but are not blocking: test-amd64-amd64-libvirt 1 build-check(1) blocked n/a test-arm64-arm64-xl-xsm 13 migrate-support-check fail never pass test-arm64-arm64-xl-xsm 14 saverestore-support-check fail never pass test-armhf-armhf-xl 13 migrate-support-check fail never pass test-armhf-armhf-xl 14 saverestore-support-check fail never pass version targeted for testing: xen a92fd9a4452cd82fa86ce1ecd6f02d53ec139c45 baseline version: xen ebe29cbd338aba99a0e17ecbdc73a25545bd219a Last test of basis 121346 2018-03-29 18:01:05 Z 0 days Testing same since 121348 2018-03-29 21:16:51 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Andre Przywara <andre.przywara@xxxxxxxxxx> Julien Grall <julien.grall@xxxxxxx> Stefano Stabellini <sstabellini@xxxxxxxxxx> jobs: build-arm64-xsm pass build-amd64 pass build-armhf pass build-amd64-libvirt fail test-armhf-armhf-xl pass test-arm64-arm64-xl-xsm pass test-amd64-amd64-xl-qemuu-debianhvm-i386 pass test-amd64-amd64-libvirt blocked ------------------------------------------------------------ sg-report-flight on osstest.test-lab.xenproject.org logs: /home/logs/logs images: /home/logs/images Logs, config files, etc. are available at http://logs.test-lab.xenproject.org/osstest/logs Explanation of these reports, and of osstest in general, is at http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master Test harness code can be found at http://xenbits.xen.org/gitweb?p=osstest.git;a=summary Not pushing. ------------------------------------------------------------ commit a92fd9a4452cd82fa86ce1ecd6f02d53ec139c45 Author: Andre Przywara <andre.przywara@xxxxxxxxxx> Date: Thu Aug 24 17:26:32 2017 +0100 ARM: VGIC: wire new VGIC(-v2) files into Xen build system Now that we have both the old VGIC prepared to cope with a sibling and the code for the new VGIC in place, lets add a Kconfig option to enable the new code and wire it into the Xen build system. This will add a compile time option to use either the "old" or the "new" VGIC. In the moment this is restricted to a vGIC-v2. To make the build system happy, we provide a temporary dummy implementation of vgic_v3_setup_hw() to allow building for now. Signed-off-by: Andre Przywara <andre.przywara@xxxxxxxxxx> Acked-by: Julien Grall <julien.grall@xxxxxxx> Acked-by: Stefano Stabellini <sstabellini@xxxxxxxxxx> commit b77d774d8274183c2252f5fbc9fa3b3b7022ba06 Author: Andre Przywara <andre.przywara@xxxxxxxxxx> Date: Thu Dec 21 12:41:28 2017 +0000 ARM: new VGIC: Allocate two pages for struct vcpu At the moment we allocate exactly one page for struct vcpu on ARM, also have a check in place to prevent it growing beyond 4KB. As the struct includes the state of all 32 private (per-VCPU) interrupts, we are at 3840 bytes on arm64 at the moment already. Growing the per-IRQ VGIC structure even slightly makes the VCPU quickly exceed the 4K limit. The new VGIC will need more space per virtual IRQ. I spent a few hours trying to trim this down, but couldn't get it below 4KB, even with the nasty hacks piling up to save some bytes here and there. It turns out that beyond efficiency, maybe, there is no real technical reason this struct has to fit in one page, so lifting the limit to two pages seems like the most pragmatic solution. Restrict the compilation error to compiling with the new VGIC and for ARM64 only. Signed-off-by: Andre Przywara <andre.przywara@xxxxxxxxxx> Acked-by: Julien Grall <julien.grall@xxxxxxx> Acked-by: Stefano Stabellini <sstabellini@xxxxxxxxxx> commit be326763e8844b8f2b4213c4f5036970e538054b Author: Andre Przywara <andre.przywara@xxxxxxxxxx> Date: Wed Feb 7 14:54:23 2018 +0000 ARM: new VGIC: vgic-init: implement map_resources map_resources is the last initialization step needed before the first VCPU is run. At that stage the code stores the MMIO base addresses used. Also it registers the respective register frames with the MMIO framework. This is based on Linux commit cbae53e663ea, written by Eric Auger. Signed-off-by: Andre Przywara <andre.przywara@xxxxxxxxxx> Acked-by: Julien Grall <julien.grall@xxxxxxx> Acked-by: Stefano Stabellini <sstabellini@xxxxxxxxxx> commit a373635990073ee3cc8df2dbb9696c868fa07114 Author: Andre Przywara <andre.przywara@xxxxxxxxxx> Date: Thu Feb 8 18:40:45 2018 +0000 ARM: new VGIC: vgic-init: implement vgic_init This patch allocates and initializes the data structures used to model the vgic distributor and virtual cpu interfaces. At that stage the number of IRQs and number of virtual CPUs is frozen. Implement the various functions that the Xen arch code is expecting to call during domain and VCPU setup to initialize the VGIC. Their prototypes are already in existing header files. This is based on Linux commit ad275b8bb1e6, written by Eric Auger. Signed-off-by: Andre Przywara <andre.przywara@xxxxxxxxxx> Reviewed-by: Julien Grall <julien.grall@xxxxxxx> Acked-by: Stefano Stabellini <sstabellini@xxxxxxxxxx> commit 848fc5948ac6a2351fb67bd52cde20ccb31e536c Author: Andre Przywara <andre.przywara@xxxxxxxxxx> Date: Wed Feb 7 14:53:03 2018 +0000 ARM: new VGIC: Add vgic_v2_enable Enable the VGIC operation by properly initialising the registers in the hypervisor GIC interface. This is based on Linux commit f7b6985cc3d0, written by Eric Auger. Signed-off-by: Andre Przywara <andre.przywara@xxxxxxxxxx> Acked-by: Julien Grall <julien.grall@xxxxxxx> Acked-by: Stefano Stabellini <sstabellini@xxxxxxxxxx> commit 3a238e4763e81f78c2730a92598bca94b20db5f4 Author: Andre Przywara <andre.przywara@xxxxxxxxxx> Date: Thu Feb 8 18:44:38 2018 +0000 ARM: new VGIC: vgic-init: register VGIC This patch implements the function which is called by Xen when it wants to register the virtual GIC. This also implements vgic_max_vcpus() for the new VGIC, which reports back the maximum number of VCPUs a certain GIC model supports. Similar to the counterpart in the "old" VGIC, we return some maximum value if the VGIC has not been initialised yet. Signed-off-by: Andre Przywara <andre.przywara@xxxxxxxxxx> Reviewed-by: Julien Grall <julien.grall@xxxxxxx> Acked-by: Stefano Stabellini <sstabellini@xxxxxxxxxx> commit 8578e5e76047fb70bf66787a041c2460798ce00f Author: Andre Przywara <andre.przywara@xxxxxxxxxx> Date: Wed Feb 7 13:58:19 2018 +0000 ARM: new VGIC: Add preliminary stub implementation The ARM arch code requires an interrupt controller emulation to implement vgic_clear_pending_irqs(), although it is suspected that it is actually not necessary. Go with a stub for now to make the linker happy. Signed-off-by: Andre Przywara <andre.przywara@xxxxxxxxxx> Reviewed-by: Julien Grall <julien.grall@xxxxxxx> Acked-by: Stefano Stabellini <sstabellini@xxxxxxxxxx> commit b7fd05b5ed5572225db9a7964220c487e40b5cf1 Author: Andre Przywara <andre.przywara@xxxxxxxxxx> Date: Mon Mar 5 11:13:36 2018 +0000 ARM: new VGIC: Implement arch_move_irqs() When a VCPU moves to another CPU, we need to adjust the target affinity of any hardware mapped vIRQs, to observe our "physical-follows-virtual" policy. Implement arch_move_irqs() to adjust the physical affinity of all hardware mapped vIRQs targetting this VCPU. Signed-off-by: Andre Przywara <andre.przywara@xxxxxxxxxx> Reviewed-by: Julien Grall <julien.grall@xxxxxxx> Acked-by: Stefano Stabellini <sstabellini@xxxxxxxxxx> (qemu changes not included) _______________________________________________ osstest-output mailing list osstest-output@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/osstest-output
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |