From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.1 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 62858C43461 for ; Sat, 5 Sep 2020 07:36:46 +0000 (UTC) Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 07A9920760 for ; Sat, 5 Sep 2020 07:36:45 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=xenproject.org header.i=@xenproject.org header.b="4Kw5acvk" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 07A9920760 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=xenproject.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=xen-devel-bounces@lists.xenproject.org Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1kESk7-0005xI-2Z; Sat, 05 Sep 2020 07:36:11 +0000 Received: from all-amaz-eas1.inumbo.com ([34.197.232.57] helo=us1-amaz-eas2.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1kESk5-0005xD-IY for xen-devel@lists.xenproject.org; Sat, 05 Sep 2020 07:36:09 +0000 X-Inumbo-ID: 17cd23bc-7da7-4b6e-80dc-ffbff6772cba Received: from mail.xenproject.org (unknown [104.130.215.37]) by us1-amaz-eas2.inumbo.com (Halon) with ESMTPS id 17cd23bc-7da7-4b6e-80dc-ffbff6772cba; Sat, 05 Sep 2020 07:36:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=xenproject.org; s=20200302mail; h=Date:From:Subject:MIME-Version: Content-Transfer-Encoding:Content-Type:Message-ID:To; bh=9N/rdFUAA4gQWU2q17le3CZmVZyP7SxvTEqBO3uD5dY=; b=4Kw5acvkW0ef/dmTJ5NOeoEk02 yaept4hEEOT7J1r2iaSReeJ95BWDUSAxQxC1+7zQabdTUkGi3XYc5Gqb5tyvyRkMtwY+H165nasgB tgoGeHWqzoIlrzsuwEEsMl6Phg7Lt/G8UZjUbFnABGf2t5yXSkcQYlQZS9UZgBLdlte0=; Received: from host146.205.237.98.conversent.net ([205.237.98.146] helo=infra.test-lab.xenproject.org) by mail.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1kESk1-0001SQ-2c; Sat, 05 Sep 2020 07:36:05 +0000 Received: from [172.16.148.1] (helo=osstest.test-lab.xenproject.org) by infra.test-lab.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1kESk0-0000Mf-RH; Sat, 05 Sep 2020 07:36:04 +0000 Received: from osstest by osstest.test-lab.xenproject.org with local (Exim 4.92) (envelope-from ) id 1kESk0-0006Hr-Qk; Sat, 05 Sep 2020 07:36:04 +0000 To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Subject: [xen-unstable-smoke test] 153741: trouble: blocked/broken X-Osstest-Failures: xen-unstable-smoke:build-amd64::broken:regression xen-unstable-smoke:build-arm64-xsm::broken:regression xen-unstable-smoke:build-armhf::broken:regression xen-unstable-smoke:build-amd64:hosts-allocate:broken:regression xen-unstable-smoke:build-armhf:hosts-allocate:broken:regression xen-unstable-smoke:build-arm64-xsm:hosts-allocate:broken:regression xen-unstable-smoke:build-amd64-libvirt:build-check(1):blocked:nonblocking xen-unstable-smoke:test-amd64-amd64-libvirt:build-check(1):blocked:nonblocking xen-unstable-smoke:test-amd64-amd64-xl-qemuu-debianhvm-amd64:build-check(1):blocked:nonblocking xen-unstable-smoke:test-arm64-arm64-xl-xsm:build-check(1):blocked:nonblocking xen-unstable-smoke:test-armhf-armhf-xl:build-check(1):blocked:nonblocking X-Osstest-Versions-This: xen=f4c1a541fa351e4f613471bbf397931f9e1ddd27 X-Osstest-Versions-That: xen=82c3d15c903aa434473dfdb570096ae5db809b94 From: osstest service owner Date: Sat, 05 Sep 2020 07:36:04 +0000 X-BeenThere: xen-devel@lists.xenproject.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Sender: "Xen-devel" flight 153741 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/153741/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 broken build-arm64-xsm broken build-armhf 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 0 days Testing same since 153728 2020-09-04 20:00:27 Z 0 days 2 attempts ------------------------------------------------------------ People who touched revisions under test: Julien Grall Stefano Stabellini Wei Chen 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 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 Reviewed-by: Bertrand Marquis Acked-by: Julien Grall commit 968bb86d04913f52d7678a842474f2a674a8b23e Author: Wei Chen 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 Reviewed-by: Bertrand Marquis Reviewed-by: Julien Grall commit 1814a626fb5811184eda64fe22f0055df4600211 Author: Julien Grall 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 Reviewed-by: Bertrand Marquis Acked-by: Stefano Stabellini (qemu changes not included)