lkml.org 
[lkml]   [2011]   [Mar]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    Subject[PATCH 0/2] do not select KALLSYMS_ALL
    Date
    UBI and UBIFS have an option to compile-in debugging support. When we enable
    debugging, compile-in various assertions, self-check functions and test modes.
    We also compile in additional verbose error messages, flash dumps and stack
    dumps.

    When we have debugging support enabled, we want to have nice stackdumps, so
    we selected KALLSYMS_ALL. But this causes various problems like unmet direct
    dependencies, reported by Randy:

    warning: (UBIFS_FS_DEBUG && LOCKDEP && LATENCYTOP) selects KALLSYMS_ALL which
    has unmet direct dependencies (DEBUG_KERNEL && KALLSYMS)

    I quickly looked at KALLSYMS_ALL and it is not immediately clear what exactly
    is the difference between KALLSYMS and KALLSYMS_ALL. And there is this
    CONFIG_KALLSYMS_EXTRA_PASS symbol, which is declared "temporary workaround"
    in the Kconfig help. This shows that this stuff is messy.

    I personally think KALLSYMS_ALL should be just merged with KALLSYMS and
    disappear - we should have only one option. CONFIG_KALLSYMS_EXTRA_PASS should
    die as well.

    But I don't want to delve into that, I choose to just forget about KALLSYMS_ALL
    and select KALLSYMS in UBI/UBIFS which seems to be enough for us.

    Artem.


    \
     
     \ /
      Last update: 2011-03-30 10:39    [from the cache]
    ©2003-2014 Jasper Spaans. hosted at Digital Ocean