From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id E6B033858C39 for ; Fri, 14 Jan 2022 21:11:32 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org E6B033858C39 Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-244-Nq3MNic_Pku2ojS9TCNkAA-1; Fri, 14 Jan 2022 16:11:31 -0500 X-MC-Unique: Nq3MNic_Pku2ojS9TCNkAA-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id B8243180A0A3; Fri, 14 Jan 2022 21:11:30 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.39.192.49]) by smtp.corp.redhat.com (Postfix) with ESMTPS id AFEE761082; Fri, 14 Jan 2022 21:11:29 +0000 (UTC) From: Florian Weimer To: Carlos O'Donell Cc: "H.J. Lu" , Carlos O'Donell via Libc-alpha Subject: Re: glibc 2.35 failures in elf/tst-cpu-features-cpuinfo-static. References: <056482b8-d413-2e24-a546-98ea46e68710@redhat.com> <87ee5aqmla.fsf@oldenburg.str.redhat.com> <87tue6p4n6.fsf@oldenburg.str.redhat.com> <51c4a93d-ab7d-f56d-0ac3-0c0a2b287e9a@redhat.com> Date: Fri, 14 Jan 2022 22:11:27 +0100 In-Reply-To: <51c4a93d-ab7d-f56d-0ac3-0c0a2b287e9a@redhat.com> (Carlos O'Donell's message of "Fri, 14 Jan 2022 16:09:42 -0500") Message-ID: <87ilumowe8.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-6.4 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2022 21:11:34 -0000 * Carlos O'Donell: > Can we make our testing detect this and mark the test XFAIL? If we treat this as our bug, we'd have to run CPUID on *all* CPUs during glibc startup. The bug is visible to applications as well. I don't think this is feasible. > Or as HJ say, blacklist the CPU from the test e.g. UNSUPPORTED? I think the bug isn't CPU-specific. Thanks, Florian