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=-0.6 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 0BE4DC2BA19 for ; Wed, 15 Apr 2020 09:17:07 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id DA56520768 for ; Wed, 15 Apr 2020 09:17:06 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="klE2fDP4" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2895225AbgDOJRD (ORCPT ); Wed, 15 Apr 2020 05:17:03 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46650 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S2895194AbgDOJQi (ORCPT ); Wed, 15 Apr 2020 05:16:38 -0400 Received: from bombadil.infradead.org (bombadil.infradead.org [IPv6:2607:7c80:54:e::133]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EAE88C061A0C for ; Wed, 15 Apr 2020 02:16:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20170209; h=In-Reply-To:Content-Transfer-Encoding :Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date: Sender:Reply-To:Content-ID:Content-Description; bh=qRxVni60JwPeuCEbMGloLeT4IZHTK64TIns0DfbAsD4=; b=klE2fDP4XMDsdmcjuIcvZ2upTU qhtzC+VsQbMmUENin8CVR7hr+xmemi0wTiWAVfNfUwqFZepusxpq/2rhBQsNBg/v5ZW2EN1z5eQ7i 6nDBJUpCtsb4TdrgcNkkId0lay6oh39c76FTl0TsyIqa/rJMZE1AcBcSEDkE5owrymUwliS+VGYJp RcSZSnA9guqilpgqAnul8iY1CwR4ymteBBjjYYyc5SqLEt3AQo6ACaZyTFVVQiCjKO6EBLpxcsvNK AbIFFzlmkjdwjdk0do/+cUTgMVJVJSawLtjyWnKZPtIp/UqKCWaSiy53ELFWbU8c0d1sjOTXcIlto wtoCaaFg==; Received: from j217100.upc-j.chello.nl ([24.132.217.100] helo=noisy.programming.kicks-ass.net) by bombadil.infradead.org with esmtpsa (Exim 4.92.3 #3 (Red Hat Linux)) id 1jOe9e-0000sD-MR; Wed, 15 Apr 2020 09:16:22 +0000 Received: from hirez.programming.kicks-ass.net (hirez.programming.kicks-ass.net [192.168.1.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by noisy.programming.kicks-ass.net (Postfix) with ESMTPS id 42DED30066E; Wed, 15 Apr 2020 11:16:20 +0200 (CEST) Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id 2674720B07BFE; Wed, 15 Apr 2020 11:16:20 +0200 (CEST) Date: Wed, 15 Apr 2020 11:16:20 +0200 From: Peter Zijlstra To: Christian =?iso-8859-1?Q?K=F6nig?= Cc: Jann Horn , Harry Wentland , Leo Li , amd-gfx@lists.freedesktop.org, Alex Deucher , "David (ChunMing) Zhou" , Thomas Gleixner , Ingo Molnar , Borislav Petkov , "H. Peter Anvin" , the arch/x86 maintainers , kernel list , Josh Poimboeuf , Andy Lutomirski , Arnaldo Carvalho de Melo , mhiramat@kernel.org Subject: Re: AMD DC graphics display code enables -mhard-float, -msse, -msse2 without any visible FPU state protection Message-ID: <20200415091620.GY20730@hirez.programming.kicks-ass.net> References: <4c5fe55d-9db9-2f61-59b2-1fb2e1b45ed0@amd.com> <20200402141308.GB20730@hirez.programming.kicks-ass.net> <20200409155956.GQ20760@hirez.programming.kicks-ass.net> <20200409170916.GR20760@hirez.programming.kicks-ass.net> <87a2f2fc-972d-ab9b-a29d-72f02d94e60e@amd.com> <20200409200125.GB2483@worktop.programming.kicks-ass.net> <56fd0509-ebef-f7b5-3ca1-fc51ca493a4c@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <56fd0509-ebef-f7b5-3ca1-fc51ca493a4c@amd.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Apr 10, 2020 at 04:31:39PM +0200, Christian König wrote: > Can we put this new automated check will be behind a configuration flag > initially? Or at least make it a warning and not a hard error. I'll try and get the patches merged in mainline objtool but with a flag that isn't used by default.