New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 893713 link

Starred by 1 user
Status: Untriaged
Owner:
snanda@chromium.org
Cc:
drinkcat@chromium.org
█ dtor@chromium.org
briannorris@chromium.org
groeck@chromium.org
sonnyrao@chromium.org
█ djkurtz@chromium.org
swboyd@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Feature



Sign in to add a comment

Any low-overhead kernel debug options that we should ship with the kernel?

Project Member Reported by diand...@chromium.org, Oct 9 
Reading through crrev.com/c/1262158 I wonder if we should be turning on things like:

CONFIG_SCHED_STACK_END_CHECK=y
CONFIG_WQ_WATCHDOG=y

...all the time in the kernel?  For CONFIG_SCHED_STACK_END_CHECK it says "The runtime overhead introduced is minimal.".  For "CONFIG_WQ_WATCHDOG" we have other watchdogs in our system, so maybe we should add this one too?

Not sure who makes decisions like this...
►

Sign in to add a comment