2011-04-05 10:21:52

by Artem Bityutskiy

[permalink] [raw]
Subject: [PATCH v2 1/2] Kconfig: improve KALLSYMS_ALL documentation

From: Artem Bityutskiy <[email protected]>

Dumb users like myself are not able to grasp from the existing KALLSYMS_ALL
documentation that this option is not what they need. Improve the help
message and make it clearer that KALLSYMS is enough in the majority of
use cases, and KALLSYMS_ALL should really be used very rarely.

Signed-off-by: Artem Bityutskiy <[email protected]>
---
init/Kconfig | 18 ++++++++++++------
1 files changed, 12 insertions(+), 6 deletions(-)

Changelog:
v1->v2:
* Spelling fix

diff --git a/init/Kconfig b/init/Kconfig
index 56240e7..563065d 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -968,12 +968,18 @@ config KALLSYMS_ALL
bool "Include all symbols in kallsyms"
depends on DEBUG_KERNEL && KALLSYMS
help
- Normally kallsyms only contains the symbols of functions, for nicer
- OOPS messages. Some debuggers can use kallsyms for other
- symbols too: say Y here to include all symbols, if you need them
- and you don't care about adding 300k to the size of your kernel.
-
- Say N.
+ Normally kallsyms only contains the symbols of functions for nicer
+ OOPS messages and backtraces (i.e., symbols from the text and inittext
+ sections). This is sufficient for most cases. And only in very rare
+ cases (e.g., when a debugger is used) all symbols are required (e.g.,
+ names of variables from the data sections, etc).
+
+ This option makes sure that all symbols are loaded into the kernel
+ image (i.e., symbols from all sections) in cost of increased kernel
+ size (depending on the kernel configuration, it may be 300KiB or
+ something like this).
+
+ Say N unless you really need all symbols.

config KALLSYMS_EXTRA_PASS
bool "Do an extra kallsyms pass"
--
1.7.2.3


2011-04-05 10:21:51

by Artem Bityutskiy

[permalink] [raw]
Subject: [PATCH v2 2/2] kbuild: move KALLSYMS_EXTRA_PASS from Kconfig to Makefile

From: Artem Bityutskiy <[email protected]>

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

Signed-off-by: Artem Bityutskiy <[email protected]>
---
Makefile | 15 ++++++++++-----
init/Kconfig | 12 ------------
2 files changed, 10 insertions(+), 17 deletions(-)

Changelog:
v1->v2:
* Allow CONFIG_KALLSYMS_EXTRA_PASS to be an environment variable
as well, not only command line argument

diff --git a/Makefile b/Makefile
index ba7a55c..58f8ab5 100644
--- a/Makefile
+++ b/Makefile
@@ -797,15 +797,17 @@ ifdef CONFIG_KALLSYMS
# o The correct .tmp_kallsyms2.o is linked into the final vmlinux.
# o Verify that the System.map from vmlinux matches the map from
# .tmp_vmlinux2, just in case we did not generate kallsyms correctly.
-# o If CONFIG_KALLSYMS_EXTRA_PASS is set, do an extra pass using
+# o If 'make KALLSYMS_EXTRA_PASS=1" was used, do an extra pass using
# .tmp_vmlinux3 and .tmp_kallsyms3.o. This is only meant as a
# temporary bypass to allow the kernel to be built while the
# maintainers work out what went wrong with kallsyms.

-ifdef CONFIG_KALLSYMS_EXTRA_PASS
-last_kallsyms := 3
-else
last_kallsyms := 2
+
+ifdef KALLSYMS_EXTRA_PASS
+ifneq ($(KALLSYMS_EXTRA_PASS),0)
+last_kallsyms := 3
+endif
endif

kallsyms.o := .tmp_kallsyms$(last_kallsyms).o
@@ -816,7 +818,8 @@ define verify_kallsyms
$(cmd_sysmap) .tmp_vmlinux$(last_kallsyms) .tmp_System.map
$(Q)cmp -s System.map .tmp_System.map || \
(echo Inconsistent kallsyms data; \
- echo Try setting CONFIG_KALLSYMS_EXTRA_PASS; \
+ echo This is a bug - please report about it; \
+ echo Try "make KALLSYMS_EXTRA_PASS=1" as a workaround; \
rm .tmp_kallsyms* ; /bin/false )
endef

@@ -1268,6 +1271,8 @@ help:
@echo ' make C=1 [targets] Check all c source with $$CHECK (sparse by default)'
@echo ' make C=2 [targets] Force check of all c source with $$CHECK'
@echo ' make W=1 [targets] Enable extra gcc checks'
+ @echo ' make KALLSYMS_EXTRA_PASS=1 [targets] Temporary workaround for kallsyms bugs'
+ @echo ' (KALLSYMS_EXTRA_PASS may also be an environment variable)'
@echo ''
@echo 'Execute "make" or "make all" to build all targets marked with [*] '
@echo 'For further info see the ./README file'
diff --git a/init/Kconfig b/init/Kconfig
index 563065d..0edda61 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -981,18 +981,6 @@ config KALLSYMS_ALL

Say N unless you really need all symbols.

-config KALLSYMS_EXTRA_PASS
- bool "Do an extra kallsyms pass"
- depends on KALLSYMS
- help
- If kallsyms is not working correctly, the build will fail with
- inconsistent kallsyms data. If that occurs, log a bug report and
- turn on KALLSYMS_EXTRA_PASS which should result in a stable build.
- Always say N here unless you find a bug in kallsyms, which must be
- reported. KALLSYMS_EXTRA_PASS is only a temporary workaround while
- you wait for kallsyms to be fixed.
-
-
config HOTPLUG
bool "Support for hot-pluggable devices" if EXPERT
default y
--
1.7.2.3

2011-04-13 10:32:42

by Artem Bityutskiy

[permalink] [raw]
Subject: Re: [PATCH v2 1/2] Kconfig: improve KALLSYMS_ALL documentation

On Tue, 2011-04-05 at 13:24 +0300, Artem Bityutskiy wrote:
> From: Artem Bityutskiy <[email protected]>
>
> Dumb users like myself are not able to grasp from the existing KALLSYMS_ALL
> documentation that this option is not what they need. Improve the help
> message and make it clearer that KALLSYMS is enough in the majority of
> use cases, and KALLSYMS_ALL should really be used very rarely.
>
> Signed-off-by: Artem Bityutskiy <[email protected]>

Michal,

what's the fate of these 2 patches? Will you merge them?

--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

2011-04-15 14:08:31

by Michal Marek

[permalink] [raw]
Subject: Re: [PATCH v2 2/2] kbuild: move KALLSYMS_EXTRA_PASS from Kconfig to Makefile

On 5.4.2011 12:24, Artem Bityutskiy wrote:
> From: Artem Bityutskiy<[email protected]>
>
> 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

2011-04-15 14:09:31

by Artem Bityutskiy

[permalink] [raw]
Subject: Re: [PATCH v2 2/2] kbuild: move KALLSYMS_EXTRA_PASS from Kconfig to Makefile

On Fri, 2011-04-15 at 16:08 +0200, Michal Marek wrote:
> 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?

Yes, fine, thank you!

--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)