From: Changbin Du <changbin.du@gmail.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Changbin Du <changbin.du@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/9] kconfig/hacking: make 'kernel hacking' menu better structurized
Date: Mon, 9 Sep 2019 22:41:32 +0800 [thread overview]
Message-ID: <20190909144130.4xvir2svtcizlc2g@mail.google.com> (raw)
In-Reply-To: <CAK7LNAQGk_4f-aGVH3bxZdNna_gdHEBHeD6DNwY49Q5kxU=U7w@mail.gmail.com>
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
prev parent reply other threads:[~2019-09-09 14:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 14:18 [PATCH v2 0/9] kconfig/hacking: make 'kernel hacking' menu better structurized Changbin Du
2019-09-09 14:18 ` [PATCH v2 1/9] kconfig/hacking: Group sysrq/kgdb/ubsan into 'Generic Kernel Debugging Instruments' Changbin Du
2019-09-09 14:18 ` [PATCH v2 2/9] kconfig/hacking: Create submenu for arch special debugging options Changbin Du
2019-09-09 14:18 ` [PATCH v2 3/9] kconfig/hacking: Group kernel data structures debugging together Changbin Du
2019-09-09 14:18 ` [PATCH v2 4/9] kconfig/hacking: Move kernel testing and coverage options to same submenu Changbin Du
2019-09-09 14:18 ` [PATCH v2 5/9] kconfig/hacking: Move Oops into 'Lockups and Hangs' Changbin Du
2019-09-09 14:18 ` [PATCH v2 6/9] kconfig/hacking: Move SCHED_STACK_END_CHECK after DEBUG_STACK_USAGE Changbin Du
2019-09-09 14:18 ` [PATCH v2 7/9] kconfig/hacking: Create a submenu for scheduler debugging options Changbin Du
2019-09-09 14:18 ` [PATCH v2 8/9] kconfig/hacking: Move DEBUG_BUGVERBOSE to 'printk and dmesg options' Changbin Du
2019-09-09 14:18 ` [PATCH v2 9/9] kconfig/hacking: Move DEBUG_FS to 'Generic Kernel Debugging Instruments' Changbin Du
2019-09-09 14:31 ` [PATCH v2 0/9] kconfig/hacking: make 'kernel hacking' menu better structurized Masahiro Yamada
2019-09-09 14:41 ` Changbin Du [this message]
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=20190909144130.4xvir2svtcizlc2g@mail.google.com \
--to=changbin.du@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
--cc=yamada.masahiro@socionext.com \
/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