mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Sam Ravnborg <sam@ravnborg.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Unhide DEBUG_RODATA if EXPERT, even if DEBUG_KERNEL=n
Date: Sun, 5 Jun 2011 11:38:07 +0200	[thread overview]
Message-ID: <20110605093807.GB19927@elte.hu> (raw)
In-Reply-To: <20110605083739.GA18560@leaf>


* Josh Triplett <josh@joshtriplett.org> wrote:

> --- a/arch/x86/Kconfig.debug
> +++ b/arch/x86/Kconfig.debug
> @@ -81,7 +81,7 @@ config X86_PTDUMP
>  config DEBUG_RODATA
>  	bool "Write protect kernel read-only data structures"
>  	default y
> -	depends on DEBUG_KERNEL
> +	depends on DEBUG_KERNEL || EXPERT

This is doing it the wrong way around. The right solution is what i 
wrote for verbose-debug: if we select DEBUG_KERNEL from EXPERT then 
you will avoid having to expand || EXPERT conditions into every 
default-enabled debug facility ...

My suggested solution will be a lot easier to maintain as well as 
under your scheme, because with your scheme we'd have to:

  - add || EXPERT every time a debug facility is enabled by default

  - remove || EXPERT every time a debug facility is switched to 
    off-by-default

If EXPERT selects DEBUG_KERNEL then we always get the right behavior, 
without polluting debug Kconfig's with EXPERT logic ...


Thanks,

	Ingo

      reply	other threads:[~2011-06-05  9:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-05  8:37 Josh Triplett
2011-06-05  9:38 ` Ingo Molnar [this message]

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=20110605093807.GB19927@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®