|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [xen-unstable-smoke test] 175926: regressions - trouble: blocked/broken/fail
flight 175926 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/175926/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 <job status> broken build-armhf <job status> broken build-armhf 4 host-install(4) broken REGR. vs. 175746 build-amd64 5 host-build-prep fail REGR. vs. 175746 build-arm64-xsm 6 xen-build fail REGR. vs. 175746 Tests which did not succeed, but are not blocking: build-amd64-libvirt 1 build-check(1) blocked n/a test-amd64-amd64-libvirt 1 build-check(1) blocked n/a test-amd64-amd64-xl-qemuu-debianhvm-amd64 1 build-check(1) blocked n/a test-arm64-arm64-xl-xsm 1 build-check(1) blocked n/a test-armhf-armhf-xl 1 build-check(1) blocked n/a version targeted for testing: xen f588e7b7cb70800533aaa8a2a9d7a4b32d10b363 baseline version: xen 6bec713f871f21c6254a5783c1e39867ea828256 Last test of basis 175746 2023-01-12 16:03:41 Z 4 days Failing since 175748 2023-01-12 20:01:56 Z 4 days 19 attempts Testing same since 175833 2023-01-14 07:00:25 Z 2 days 17 attempts ------------------------------------------------------------ People who touched revisions under test: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Julien Grall <jgrall@xxxxxxxxxx> Michal Orzel <michal.orzel@xxxxxxx> Stefano Stabellini <sstabellini@xxxxxxxxxx> jobs: build-arm64-xsm fail build-amd64 broken build-armhf broken build-amd64-libvirt blocked test-armhf-armhf-xl blocked test-arm64-arm64-xl-xsm blocked test-amd64-amd64-xl-qemuu-debianhvm-amd64 blocked 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 broken-job build-amd64 broken broken-job build-armhf broken broken-step build-armhf host-install(4) Not pushing. ------------------------------------------------------------ commit f588e7b7cb70800533aaa8a2a9d7a4b32d10b363 Author: Michal Orzel <michal.orzel@xxxxxxx> Date: Tue Jan 3 11:25:19 2023 +0100 xen/arm: Add 0x prefix when printing memory size in construct_domU Printing memory size in hex without 0x prefix can be misleading, so add it. Also, take the opportunity to adhere to 80 chars line length limit by moving the printk arguments to the next line. Signed-off-by: Michal Orzel <michal.orzel@xxxxxxx> Reviewed-by: Ayan Kumar Halder <ayan.kumar.halder@xxxxxxx> Acked-by: Julien Grall <jgrall@xxxxxxxxxx> commit 229ebd517b9df0e2d2f9e3ea50b57ca716334826 Author: Julien Grall <jgrall@xxxxxxxxxx> Date: Thu Jan 12 22:07:42 2023 +0000 xen/arm: linker: The identitymap check should cover the whole .text.header At the moment, we are only checking that only some part of .text.header is part of the identity mapping. However, this doesn't take into account the literal pool which will be located at the end of the section. While we could try to avoid using a literal pool, in the near future we will also want to use an identity mapping for switch_ttbr(). Not everything in .text.header requires to be part of the identity mapping. But it is below a page size (i.e. 4KB) so take a shortcut and check that .text.header is smaller than a page size. With that _end_boot can be removed as it is now unused. Take the opportunity to avoid assuming that a page size is always 4KB in the error message and comment. Signed-off-by: Julien Grall <jgrall@xxxxxxxxxx> Reviewed-by: Stefano Stabellini <sstabellini@xxxxxxxxxx> commit 22a9981ba2443bd569bad6b772fb6e7e64f0d714 Author: Julien Grall <jgrall@xxxxxxxxxx> Date: Thu Jan 12 22:06:42 2023 +0000 xen/arm: linker: Indent correctly _stext _stext is indented by one space more compare to the lines. This doesn't seem warrant, so delete the extra space. Signed-off: Julien Grall <jgrall@xxxxxxxxxx> Acked-by: Stefano Stabellini <sstabellini@xxxxxxxxxx> commit 3edca52ce736297d7fcf293860cd94ef62638052 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Mon Jan 9 10:58:31 2023 +0000 x86/vmx: Support for CPUs without model-specific LBR Ice Lake (server at least) has both architectural LBR and model-specific LBR. Sapphire Rapids does not have model-specific LBR at all. I.e. On SPR and later, model_specific_lbr will always be NULL, so we must make changes to avoid reliably hitting the domain_crash(). The Arch LBR spec states that CPUs without model-specific LBR implement MSR_DBG_CTL.LBR by discarding writes and always returning 0. Do this for any CPU for which we lack model-specific LBR information. Adjust the now-stale comment, now that the Arch LBR spec has created a way to signal "no model specific LBR" to guests. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Kevin Tian <kevin.tian@xxxxxxxxx> commit e94af0d58f86c3a914b9cbbf4d9ed3d43b974771 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Mon Jan 9 11:42:22 2023 +0000 x86/vmx: Calculate model-specific LBRs once at start of day There is no point repeating this calculation at runtime, especially as it is in the fallback path of the WRSMR/RDMSR handlers. Move the infrastructure higher in vmx.c to avoid forward declarations, renaming last_branch_msr_get() to get_model_specific_lbr() to highlight that these are model-specific only. No practical change. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Kevin Tian <kevin.tian@xxxxxxxxx> commit e6ee01ad24b6a1c3b922579964deebb119a90a48 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Tue Jan 3 15:08:56 2023 +0000 xen/version: Drop compat/kernel.c kernel.c is mostly in an #ifndef COMPAT guard, because compat/kernel.c re-includes kernel.c to recompile xen_version() in a compat form. However, the xen_version hypercall is almost guest-ABI-agnostic; only XENVER_platform_parameters has a compat split. Handle this locally, and do away with the re-include entirely. Also drop the CHECK_TYPE()'s between types that are simply char-arrays in their native and compat form. In particular, this removed the final instances of obfuscation via the DO() macro. No functional change. Also saves 2k of of .text in the x86 build. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit 73f0696dc1d31a987563184ce1d01cbf5d12d6ab Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Tue Dec 20 15:51:07 2022 +0000 public/version: Change xen_feature_info to have a fixed size This is technically an ABI change, but Xen doesn't operate in any environment where "unsigned int" is different to uint32_t, so switch to the explicit form. This avoids the need to derive (identical) compat logic for handling the subop. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Acked-by: Julien Grall <jgrall@xxxxxxxxxx> (qemu changes not included)
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |