mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	the arch/x86 maintainers <x86@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Miroslav Benes <mbenes@suse.cz>
Subject: Re: objtool warnings for kernel/trace/trace_selftest_dynamic.o
Date: Mon, 17 Dec 2018 15:54:28 -0800	[thread overview]
Message-ID: <20181217235428.GY25620@tassilo.jf.intel.com> (raw)
In-Reply-To: <20181217213126.lsqhyszoulel6uq6@treble>

On Mon, Dec 17, 2018 at 03:31:26PM -0600, Josh Poimboeuf wrote:
> On Mon, Dec 17, 2018 at 08:29:38PM +0100, Peter Zijlstra wrote:
> > On Mon, Dec 17, 2018 at 12:16:38PM -0600, Josh Poimboeuf wrote:
> > 
> > > > Yes LTO causes the to be treated like static functions.
> > > > 
> > > > I guess noclone is unlikely to be really needed here because these
> > > > functions are unlikely to be cloned.
> > > > 
> > > > So as a workaround it could be removed.
> > > > 
> > > > But note we have other noclone functions in the tree (like in KVM)
> > > > which actually need it.
> > > 
> > > How about we just use the __used attribute then?  It seems to have the
> > > same result of preventing IPA optimizations (without the weird side
> > > effect of missing frame pointers).
> > 
> > AFAIK we don't have any in-tree LTO, so it can all go in the bin.
> > 
> > When/if we get the LTO trainwreck sorted -- which very much includes
> > getting that memory-order-consume fixed -- we can revisit all that.
> 
> Ok, then if there are no objections I'll just send a revert of:
> 
>   dd3dad0d716d ("ftrace: Mark function tracer test functions noinline/noclone")

I object to that.

-Andi

  parent reply	other threads:[~2018-12-17 23:54 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-16 18:33 Arnd Bergmann
2018-12-17 17:39 ` Josh Poimboeuf
2018-12-17 18:04   ` Andi Kleen
2018-12-17 18:16     ` Josh Poimboeuf
2018-12-17 19:29       ` Peter Zijlstra
2018-12-17 20:55         ` Andi Kleen
2018-12-17 22:35           ` Peter Zijlstra
2018-12-17 23:59             ` Andi Kleen
2018-12-18  9:19               ` Peter Zijlstra
2018-12-18 21:22                 ` Andi Kleen
2018-12-17 21:31         ` Josh Poimboeuf
2018-12-17 22:36           ` Steven Rostedt
2018-12-18  0:06             ` Andi Kleen
2018-12-18  2:49               ` Josh Poimboeuf
2018-12-18  4:22                 ` Andi Kleen
2018-12-18  9:28                 ` Miroslav Benes
2018-12-18 12:15                   ` Martin Jambor
2018-12-18 12:31                     ` Steven Rostedt
2018-12-18 14:01                     ` Josh Poimboeuf
2018-12-18 21:20                       ` Andi Kleen
2018-12-19  3:44                         ` Sean Christopherson
2018-12-19 17:31                       ` Martin Jambor
2018-12-18 21:15                     ` Andi Kleen
2018-12-18 21:57                       ` Steven Rostedt
2018-12-18 22:13                         ` Andi Kleen
2018-12-18 22:16                           ` Steven Rostedt
2018-12-18 23:26                             ` Andi Kleen
2018-12-18 23:40                               ` Steven Rostedt
2018-12-19 17:38                       ` Martin Jambor
2018-12-18  3:05             ` Josh Poimboeuf
2018-12-17 23:54           ` Andi Kleen [this message]
2018-12-17 21:03       ` Andi Kleen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181217235428.GY25620@tassilo.jf.intel.com \
    --to=ak@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbenes@suse.cz \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome