Messages in this thread | | | Date | Mon, 9 Sep 2019 22:41:32 +0800 | From | Changbin Du <> | Subject | Re: [PATCH v2 0/9] kconfig/hacking: make 'kernel hacking' menu better structurized |
| |
On Mon, Sep 09, 2019 at 11:31:10PM +0900, Masahiro Yamada wrote: > Hi. > > On Mon, Sep 9, 2019 at 11:18 PM Changbin Du <changbin.du@gmail.com> 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. > > > Could you please change the subject prefix "kconfig/hacking:" ? > ("hacking:" , "debug:" or whatever, but no "kconfig") > sure, I pick 'hacking'.
> I just opened this thread just in case it might be related to kconfig, > but it was not. > > Thanks. > > > > > > > > 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 > │ > > └─────────────────────────────────────────────────────────────────────────────┘ > > > > 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): > > kconfig/hacking: Group sysrq/kgdb/ubsan into 'Generic Kernel Debugging > > Instruments' > > kconfig/hacking: Create submenu for arch special debugging options > > kconfig/hacking: Group kernel data structures debugging together > > kconfig/hacking: Move kernel testing and coverage options to same > > submenu > > kconfig/hacking: Move Oops into 'Lockups and Hangs' > > kconfig/hacking: Move SCHED_STACK_END_CHECK after DEBUG_STACK_USAGE > > kconfig/hacking: Create a submenu for scheduler debugging options > > kconfig/hacking: Move DEBUG_BUGVERBOSE to 'printk and dmesg options' > > kconfig/hacking: Move DEBUG_FS to 'Generic Kernel Debugging > > Instruments' > > > > lib/Kconfig.debug | 659 ++++++++++++++++++++++++---------------------- > > 1 file changed, 340 insertions(+), 319 deletions(-) > > > > -- > > 2.20.1 > > > > > -- > Best Regards > Masahiro Yamada
-- Cheers, Changbin Du
| |