All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Rientjes <rientjes@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Borislav Petkov <bp@alien8.de>,
	LKML <linux-kernel@vger.kernel.org>, X86 ML <x86@kernel.org>,
	Richard Weinberger <richard@nod.at>, Borislav Petkov <bp@suse.de>
Subject: Re: [PATCH] Clarify CONFIG_DEBUG_INFO's bloaty nature
Date: Wed, 5 Feb 2014 06:46:13 +0100	[thread overview]
Message-ID: <20140205054613.GA30094@gmail.com> (raw)
In-Reply-To: <CA+55aFzXvPseHVZOk82hTpFrQYRnHnq-5TBz5Jw__wuktUgi2w@mail.gmail.com>


* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Tue, Feb 4, 2014 at 1:08 AM, Ingo Molnar <mingo@kernel.org> wrote:
> >
> >  config SAVE_TIME_AND_DISK_SPACE
> >         bool "Faster and leaner build object files: compile without debug info"
> >         default y
> 
> Thinking about it, we already have this. It's called "CONFIG_COMPILE_TEST".
> 
> It very much gets set by all{yes,mod}config, and it also says "we're
> interested in testing the compile, not so much running the result".
> 
> So let's just make the DEBUG_INFO depend on !COMPILE_TEST.
> 
> Trivial oneliner patch (independent of the discussion about improving
> the documentation), so I'll just apply it.
> 
> I can't imagine that this would be controversial:
> 
>    config DEBUG_INFO
>           bool "Compile the kernel with debug info"
>   -       depends on DEBUG_KERNEL
>   +       depends on DEBUG_KERNEL && !COMPILE_TEST
>           help
> 
> Hm?

Fully agreed.

Thanks,

	Ingo

  parent reply	other threads:[~2014-02-05  5:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03 18:29 [PATCH] Clarify CONFIG_DEBUG_INFO's bloaty nature Borislav Petkov
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             ` Ingo Molnar [this message]
2014-02-04  4:59       ` [PATCH] Clarify CONFIG_DEBUG_INFO's bloaty nature 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=20140205054613.GA30094@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=bp@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard@nod.at \
    --cc=rientjes@google.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.