Re: [PATCH v3 0/9] hacking: make 'kernel hacking' menu better structurized
From: Randy Dunlap
Date: Mon Sep 09 2019 - 12:55:55 EST
On 9/9/19 7:44 AM, Changbin Du wrote:
> This series is a trivial improvment for the layout of 'kernel hacking'
> configuration menu. Now we have many items in it which makes takes
> a little time to look up them since they are not well structurized yet.
>
> Early discussion is here:
> https://lkml.org/lkml/2019/9/1/39
>
> This is a preview:
>
> â âââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ â
> â â printk and dmesg options ---> â â
> â â Compile-time checks and compiler options ---> â â
> â â Generic Kernel Debugging Instruments ---> â â
> â â -*- Kernel debugging â â
> â â [*] Miscellaneous debug code â â
> â â Memory Debugging ---> â â
> â â [ ] Debug shared IRQ handlers â â
> â â Debug Oops, Lockups and Hangs ---> â â
> â â Scheduler Debugging ---> â â
> â â [*] Enable extra timekeeping sanity checking â â
> â â Lock Debugging (spinlocks, mutexes, etc...) ---> â â
> â â -*- Stack backtrace support â â
> â â [ ] Warn for all uses of unseeded randomness â â
> â â [ ] kobject debugging â â
> â â Debug kernel data structures ---> â â
> â â [ ] Debug credential management â â
> â â RCU Debugging ---> â â
> â â [ ] Force round-robin CPU selection for unbound work items â â
> â â [ ] Force extended block device numbers and spread them â â
> â â [ ] Enable CPU hotplug state control â â
> â â [*] Latency measuring infrastructure â â
> â â [*] Tracers ---> â â
> â â [ ] Remote debugging over FireWire early on boot â â
> â â [*] Sample kernel code ---> â â
> â â [*] Filter access to /dev/mem â â
> â â [ ] Filter I/O access to /dev/mem â â
> â â [ ] Additional debug code for syzbot â â
> â â x86 Debugging ---> â â
> â â Kernel Testing and Coverage ---> â â
> â â â â
> â â â â
> â âââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ â
> âââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
> â <Select> < Exit > < Help > < Save > < Load > â
> âââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
>
> v3:
> o change subject prefix.
> v2:
> o rebase to linux-next.
> o move DEBUG_FS to 'Generic Kernel Debugging Instruments'
> o move DEBUG_NOTIFIERS to 'Debug kernel data structures'
>
> Changbin Du (9):
> hacking: Group sysrq/kgdb/ubsan into 'Generic Kernel Debugging
> Instruments'
> hacking: Create submenu for arch special debugging options
> hacking: Group kernel data structures debugging together
> hacking: Move kernel testing and coverage options to same submenu
> hacking: Move Oops into 'Lockups and Hangs'
> hacking: Move SCHED_STACK_END_CHECK after DEBUG_STACK_USAGE
> hacking: Create a submenu for scheduler debugging options
> hacking: Move DEBUG_BUGVERBOSE to 'printk and dmesg options'
> hacking: Move DEBUG_FS to 'Generic Kernel Debugging Instruments'
>
> lib/Kconfig.debug | 659 ++++++++++++++++++++++++----------------------
> 1 file changed, 340 insertions(+), 319 deletions(-)
Hi,
Looks good to me.
I verified that the before and after kernel .config file contains the same
symbols and values (for allmodconfig).
I also tested with menuconfig, nconfig, gconfig, and xconfig.
for all 9 patches:
Acked-by: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
Tested-by: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
Thanks.
--
~Randy