* [xen-unstable-smoke test] 153756: trouble: blocked/broken
@ 2020-09-05 17:33 osstest service owner
0 siblings, 0 replies; only message in thread
From: osstest service owner @ 2020-09-05 17:33 UTC (permalink / raw)
To: xen-devel, osstest-admin
flight 153756 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/153756/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 <job status> broken
build-arm64-xsm <job status> broken
build-armhf <job status> broken
build-amd64 2 hosts-allocate broken REGR. vs. 153720
build-armhf 2 hosts-allocate broken REGR. vs. 153720
build-arm64-xsm 2 hosts-allocate broken REGR. vs. 153720
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 f4c1a541fa351e4f613471bbf397931f9e1ddd27
baseline version:
xen 82c3d15c903aa434473dfdb570096ae5db809b94
Last test of basis 153720 2020-09-04 17:01:26 Z 1 days
Testing same since 153728 2020-09-04 20:00:27 Z 0 days 4 attempts
------------------------------------------------------------
People who touched revisions under test:
Julien Grall <jgrall@amazon.com>
Stefano Stabellini <sstabellini@kernel.org>
Wei Chen <wei.chen@arm.com>
jobs:
build-arm64-xsm broken
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-arm64-xsm broken
broken-job build-armhf broken
broken-step build-amd64 hosts-allocate
broken-step build-armhf hosts-allocate
broken-step build-arm64-xsm hosts-allocate
Not pushing.
------------------------------------------------------------
commit f4c1a541fa351e4f613471bbf397931f9e1ddd27
Author: Wei Chen <wei.chen@arm.com>
Date: Fri Aug 28 02:34:04 2020 +0000
xen/arm: Throw messages for unknown FP/SIMD implement ID
Arm ID_AA64PFR0_EL1 register provides two fields to describe CPU
FP/SIMD implementations. Currently, we exactly know the meaning of
0x0, 0x1 and 0xf of these fields. Xen treats value < 8 as FP/SIMD
features presented. If there is a value 0x2 bumped in the future,
Xen behaviors for value <= 0x1 can also take effect. But what Xen
done for value <= 0x1 may not always cover new value 0x2 required.
We throw these messages to break the silence when Xen detected
unknown FP/SIMD IDs to notice user to check.
Signed-off-by: Wei Chen <wei.chen@arm.com>
Reviewed-by: Bertrand Marquis <bertrand.marquis@arm.com>
Acked-by: Julien Grall <jgrall@amazon.com>
commit 968bb86d04913f52d7678a842474f2a674a8b23e
Author: Wei Chen <wei.chen@arm.com>
Date: Fri Aug 28 02:34:03 2020 +0000
xen/arm: Missing N1/A76/A75 FP registers in vCPU context switch
Xen has cpu_has_fp/cpu_has_simd to detect whether the CPU supports
FP/SIMD or not. But currently, these two MACROs only consider value 0
of ID_AA64PFR0_EL1.FP/SIMD as FP/SIMD features enabled. But for CPUs
that support FP/SIMD and half-precision floating-point arithmetic, the
ID_AA64PFR0_EL1.FP/SIMD are 1 (see Arm ARM DDI0487F.b, D13.2.64).
For these CPUs, xen will treat them as no FP/SIMD support, the
vfp_save/restore_state will not take effect.
From the TRM documents of Cortex-A75/A76/N1, we know these CPUs support
basic Advanced SIMD/FP and half-precision floating-point arithmetic. In
this case, on N1/A76/A75 platforms, Xen will always miss the floating
pointer registers save/restore. If different vCPUs are running on the
same pCPU, the floating pointer registers will be corrupted randomly.
This patch fixes Xen on these new cores.
Signed-off-by: Wei Chen <wei.chen@arm.com>
Reviewed-by: Bertrand Marquis <bertrand.marquis@arm.com>
Reviewed-by: Julien Grall <jgrall@amazon.com>
commit 1814a626fb5811184eda64fe22f0055df4600211
Author: Julien Grall <jgrall@amazon.com>
Date: Tue Aug 25 18:38:10 2020 +0100
xen/arm: Update silicon-errata.txt with the Neovers AT erratum
Commit 858c0be8c2fa "xen/arm: Enable CPU Erratum 1165522 for Neoverse"
added a new erratum but forgot to update silicon-errata.txt.
Update the file accordingly to keep track of errata workaround in Xen.
Signed-off-by: Julien Grall <jgrall@amazon.com>
Reviewed-by: Bertrand Marquis <bertrand.marquis@arm.com>
Acked-by: Stefano Stabellini <sstabellini@kernel.org>
(qemu changes not included)
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-09-05 17:34 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-09-05 17:33 [xen-unstable-smoke test] 153756: trouble: blocked/broken osstest service owner
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.