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=-2.5 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_MUTT autolearn=ham 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 5C9ACC43387 for ; Tue, 18 Dec 2018 21:22:41 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 352C2217D9 for ; Tue, 18 Dec 2018 21:22:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727209AbeLRVWk (ORCPT ); Tue, 18 Dec 2018 16:22:40 -0500 Received: from mga07.intel.com ([134.134.136.100]:33605 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726570AbeLRVWj (ORCPT ); Tue, 18 Dec 2018 16:22:39 -0500 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Dec 2018 13:22:38 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,370,1539673200"; d="scan'208";a="102547923" Received: from tassilo.jf.intel.com (HELO tassilo.localdomain) ([10.7.201.137]) by orsmga008.jf.intel.com with ESMTP; 18 Dec 2018 13:22:39 -0800 Received: by tassilo.localdomain (Postfix, from userid 1000) id 19DE2300B49; Tue, 18 Dec 2018 13:22:39 -0800 (PST) Date: Tue, 18 Dec 2018 13:22:39 -0800 From: Andi Kleen To: Peter Zijlstra Cc: Josh Poimboeuf , Arnd Bergmann , Linux Kernel Mailing List , the arch/x86 maintainers , Steven Rostedt , Miroslav Benes Subject: Re: objtool warnings for kernel/trace/trace_selftest_dynamic.o Message-ID: <20181218212239.GF25620@tassilo.jf.intel.com> References: <20181217173900.ygifx7khwmzn2gv2@treble> <20181217180434.GS25620@tassilo.jf.intel.com> <20181217181638.dfexg6mkmbfyzfli@treble> <20181217192938.GF2218@hirez.programming.kicks-ass.net> <20181217205535.GT25620@tassilo.jf.intel.com> <20181217223524.GH2218@hirez.programming.kicks-ass.net> <20181217235950.GZ25620@tassilo.jf.intel.com> <20181218091932.GJ2218@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181218091932.GJ2218@hirez.programming.kicks-ass.net> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Dec 18, 2018 at 10:19:32AM +0100, Peter Zijlstra wrote: > On Mon, Dec 17, 2018 at 03:59:50PM -0800, Andi Kleen wrote: > > BTW I have a user base for LTO and so far noone has reported any issues > > like this. > > Because ordering issues are immediately obvious and easy to debug no > doubt. Again if it's a real problem it should be already there because we have a lot of code inside files that gets happily inlined. Do you have an example in the tree where it happened or could happen? -Andi