mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: X86 ML <x86@kernel.org>, Richard Weinberger <richard@nod.at>,
	Borislav Petkov <bp@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: [PATCH] Clarify CONFIG_DEBUG_INFO's bloaty nature
Date: Mon,  3 Feb 2014 19:29:43 +0100	[thread overview]
Message-ID: <1391452183-2160-1-git-send-email-bp@alien8.de> (raw)

From: Borislav Petkov <bp@suse.de>

Hold down when it makes sense to enable CONFIG_DEBUG_INFO and when
CONFIG_KALLSYMS suffices.

Signed-off-by: Borislav Petkov <bp@suse.de>
Link: http://lkml.kernel.org/r/CA%2B55aFw_xs1tUteDrXz21QZB7BFk5p%2BF5NZ-SpV=CUVjeFwapA@mail.gmail.com
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
---
 lib/Kconfig.debug | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index dbf94a7d25a8..9095c2078095 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -126,7 +126,11 @@ config DEBUG_INFO
 	  This adds debug symbols to the kernel and modules (gcc -g), and
 	  is needed if you intend to use kernel crashdump or binary object
 	  tools like crash, kgdb, LKCD, gdb, etc on the kernel.
-	  Say Y here only if you plan to debug the kernel.
+
+	  If you only want to have resolved symbols in kernel traces and
+	  are not going to need support for those tools above, you don't need
+	  to enable this as it is a huge bloat and build slowdown;
+	  enable CONFIG_KALLSYMS instead.
 
 	  If unsure, say N.
 
-- 
1.8.5.2.192.g7794a68


             reply	other threads:[~2014-02-03 18:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03 18:29 Borislav Petkov [this message]
2014-02-03 22:00 ` David Rientjes
2014-02-03 22:47   ` Linus Torvalds
2014-02-03 22:57     ` Andrew Morton
2014-02-03 23:34       ` David Rientjes
2014-02-04  9:08         ` Ingo Molnar
2014-02-04 16:36           ` Linus Torvalds
2014-02-04 17:32             ` Andi Kleen
2014-02-04 18:41               ` Linus Torvalds
2014-02-05  5:51                 ` [PATCH] x86: Disable CONFIG_X86_DECODER_SELFTEST in allmod/allyesconfigs Ingo Molnar
2014-02-05 16:17                   ` Paul Gortmaker
2014-02-05 17:32                     ` Andi Kleen
2014-02-10 13:31                   ` [tip:x86/urgent] x86/debug: " tip-bot for Ingo Molnar
2014-02-11  0:01                   ` [PATCH] x86: " Stephen Rothwell
2014-02-11  7:14                     ` Ingo Molnar
2014-02-05  5:46             ` [PATCH] Clarify CONFIG_DEBUG_INFO's bloaty nature Ingo Molnar
2014-02-04  4:59       ` Borislav Petkov

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=1391452183-2160-1-git-send-email-bp@alien8.de \
    --to=bp@alien8.de \
    --cc=akpm@linux-foundation.org \
    --cc=bp@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard@nod.at \
    --cc=torvalds@linux-foundation.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