mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Du Changbin <changbin.du@gmail.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Du Changbin <changbin.du@gmail.com>,
	yamada.masahiro@socionext.com, michal.lkml@markovi.net,
	tglx@linutronix.de, mingo@redhat.com, linux@armlinux.org.uk,
	akpm@linux-foundation.org, linux-kbuild@vger.kernel.org,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	rostedt@goodmis.org, Changbin Du <changbin.du@intel.com>,
	linux-sparse@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/4] kernel hacking: new config NO_AUTO_INLINE to disable compiler auto-inline optimizations
Date: Thu, 18 Oct 2018 17:01:49 +0000	[thread overview]
Message-ID: <20181018170148.47zbtfno5cjh4wb6@mail.google.com> (raw)
In-Reply-To: <62bcdf3d-87be-407f-b971-5a53dbb1e4b8@arm.com>

On Thu, Oct 18, 2018 at 05:57:56PM +0100, Robin Murphy wrote:
> On 18/10/18 17:25, Du Changbin wrote:
> > From: Changbin Du <changbin.du@intel.com>
> > 
> > This patch add a new kernel hacking option NO_AUTO_INLINE. Selecting
> > this option will prevent the compiler from optimizing the kernel by
> > auto-inlining functions not marked with the inline keyword.
> > 
> > With this option, only functions explicitly marked with "inline" will
> > be inlined. This will allow the function tracer to trace more functions
> > because it only traces functions that the compiler has not inlined.
> > 
> > Signed-off-by: Changbin Du <changbin.du@intel.com>
> > Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
> > ---
> >   Makefile          |  6 ++++++
> >   lib/Kconfig.debug | 25 +++++++++++++++++++++++++
> >   2 files changed, 31 insertions(+)
> > 
> > diff --git a/Makefile b/Makefile
> > index e8b599b4dcde..757d6507cb5c 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -749,6 +749,12 @@ KBUILD_CFLAGS 	+= $(call cc-option, -femit-struct-debug-baseonly) \
> >   		   $(call cc-option,-fno-var-tracking)
> >   endif
> > +ifdef CONFIG_NO_AUTO_INLINE
> > +KBUILD_CFLAGS   += $(call cc-option, -fno-inline-functions) \
> > +		   $(call cc-option, -fno-inline-small-functions) \
> > +		   $(call cc-option, -fno-inline-functions-called-once)
> > +endif
> > +
> >   ifdef CONFIG_FUNCTION_TRACER
> >   ifdef CONFIG_FTRACE_MCOUNT_RECORD
> >     # gcc 5 supports generating the mcount tables directly
> > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> > index 4966c4fbe7f7..0f9b4fa78b1c 100644
> > --- a/lib/Kconfig.debug
> > +++ b/lib/Kconfig.debug
> > @@ -211,6 +211,31 @@ config GDB_SCRIPTS
> >   	  instance. See Documentation/dev-tools/gdb-kernel-debugging.rst
> >   	  for further details.
> > +config NO_AUTO_INLINE
> > +	bool "Disable compiler auto-inline optimizations"
> > +	help
> > +	  This will prevent the compiler from optimizing the kernel by
> > +	  auto-inlining functions not marked with the inline keyword.
> > +	  With this option, only functions explicitly marked with
> > +	  "inline" will be inlined. This will allow the function tracer
> > +	  to trace more functions because it only traces functions that
> > +	  the compiler has not inlined.
> > +
> > +	  Enabling this function can help debugging a kernel if using
> > +	  the function tracer. But it can also change how the kernel
> > +	  works, because inlining functions may change the timing,
> > +	  which could make it difficult while debugging race conditions.
> > +
> > +	  If unsure, select N.
> > +
> > +config ENABLE_WARN_DEPRECATED
> 
> This part doesn't look like it belongs in this patch, and judging by the
> commit message in 771c035372a0 wouldn't be welcome back anyway.
> 
opps, this is a rebasing mistake. Let me update it. Thanks.

> Robin.
> 
> > +	bool "Enable __deprecated logic"
> > +	default y
> > +	help
> > +	  Enable the __deprecated logic in the kernel build.
> > +	  Disable this to suppress the "warning: 'foo' is deprecated
> > +	  (declared at kernel/power/somefile.c:1234)" messages.
> > +
> >   config ENABLE_MUST_CHECK
> >   	bool "Enable __must_check logic"
> >   	default y
> > 

-- 
Thanks,
Du Changbin

  reply	other threads:[~2018-10-18 17:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18 16:25 [PATCH 0/4] kernel hacking: GCC optimization for better debug experience (-Og) Du Changbin
2018-10-18 16:25 ` [PATCH 1/4] x86/mm: surround level4_kernel_pgt with #ifdef CONFIG_X86_5LEVEL...#endif Du Changbin
2018-10-18 16:25 ` [PATCH 2/4] kernel hacking: new config NO_AUTO_INLINE to disable compiler auto-inline optimizations Du Changbin
2018-10-18 16:57   ` Robin Murphy
2018-10-18 17:01     ` Du Changbin [this message]
2018-10-18 16:59   ` Steven Rostedt
2018-10-18 17:03     ` Du Changbin
2018-10-18 16:25 ` [PATCH 3/4] ARM: mm: fix build error in fix_to_virt with CONFIG_CC_OPTIMIZE_FOR_DEBUGGING Du Changbin
2018-10-18 16:25 ` [PATCH 4/4] kernel hacking: new config CC_OPTIMIZE_FOR_DEBUGGING to apply GCC -Og optimization Du Changbin

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=20181018170148.47zbtfno5cjh4wb6@mail.google.com \
    --to=changbin.du@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=changbin.du@intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=michal.lkml@markovi.net \
    --cc=mingo@redhat.com \
    --cc=robin.murphy@arm.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=yamada.masahiro@socionext.com \
    /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

all inboxes | Powered by JetHome®