public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	Paulo Marques <pmarques@grupopie.com>,
	Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: [PATCH v2 2/2] kbuild: move KALLSYMS_EXTRA_PASS from Kconfig to Makefile
Date: Fri, 15 Apr 2011 16:08:28 +0200	[thread overview]
Message-ID: <4DA8515C.4050905@suse.cz> (raw)
In-Reply-To: <1301999098-21412-2-git-send-email-dedekind1@gmail.com>

On 5.4.2011 12:24, Artem Bityutskiy wrote:
> From: Artem Bityutskiy<Artem.Bityutskiy@nokia.com>
>
> At the moment we have the CONFIG_KALLSYMS_EXTRA_PASS Kconfig switch,
> which users can enable or disable while configuring the kernel. This
> option is then used by 'make' to determine whether an extra kallsyms
> pass is needed or not.
>
> However, this approach is not nice and confusing, and this patch moves
> CONFIG_KALLSYMS_EXTRA_PASS from Kconfig to Makefile instead. The
> rationale is below.
>
> 1. CONFIG_KALLSYMS_EXTRA_PASS is really about the build time, not
>     run-time. There is no real need for it to be in Kconfig. It is
>     just an additional work-around which should be used only in rare
>     cases, when someone breaks kallsyms, so Kbuild/Makefile is much
>     better place for this option.
> 2. Grepping CONFIG_KALLSYMS_EXTRA_PASS shows that many defconfigs have
>     it enabled, probably not because they try to work-around a kallsyms
>     bug, but just because the Kconfig help text is confusing and does
>     not really make it clear that this option should not be used unless
>     except when kallsyms is broken.
> 3. And since many people have CONFIG_KALLSYMS_EXTRA_PASS enabled in
>     their Kconfig, we do might fail to notice kallsyms bugs in time. E.g.,
>     many testers use "make allyesconfig" to test builds, which will enable
>     CONFIG_KALLSYMS_EXTRA_PASS and kallsyms breakage will not be noticed.
>
> To address that, this patch:
>
> 1. Kills CONFIG_KALLSYMS_EXTRA_PASS
> 2. Changes Makefile so that people can use "make KALLSYMS_EXTRA_PASS=1"
>     to enable the extra pass if needed. Additionally, they may define
>     KALLSYMS_EXTRA_PASS as an environment variable.
> 3. By default KALLSYMS_EXTRA_PASS is disabled and if kallsyms has issues,
>     "make" should print a warning and suggest using KALLSYMS_EXTRA_PASS
> 4. Add "make help" entry for KALLSYMS_EXTRA_PASS

I merged the patches, but removed the make help text. Rationale: People 
who don't need it don't need the help text, for those that need it the 
help text wouldn't provide more information than the error message. Is 
this OK with you?

Michal

  reply	other threads:[~2011-04-15 14:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-05 10:24 [PATCH v2 1/2] Kconfig: improve KALLSYMS_ALL documentation Artem Bityutskiy
2011-04-05 10:24 ` [PATCH v2 2/2] kbuild: move KALLSYMS_EXTRA_PASS from Kconfig to Makefile Artem Bityutskiy
2011-04-15 14:08   ` Michal Marek [this message]
2011-04-15 14:06     ` Artem Bityutskiy
2011-04-13 10:22 ` [PATCH v2 1/2] Kconfig: improve KALLSYMS_ALL documentation Artem Bityutskiy

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=4DA8515C.4050905@suse.cz \
    --to=mmarek@suse.cz \
    --cc=dedekind1@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmarques@grupopie.com \
    --cc=rdunlap@xenotime.net \
    /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