Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add scripts for building in a container #9

Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
init: allow schedule statistics to be chosen without DEBUG_KERNEL
TAG_MSFT: lcow

Signed-off-by: Sinan Kaya <sinan.kaya@microsoft.com>
Signed-off-by: Pavel Tatashin <pasha.tatashin@soleen.com>
  • Loading branch information
franksinankaya authored and Sasha Levin committed Jun 26, 2019
commit b16a2b8488cb3cb3dd7b0ec79b977d1f312ef699
7 changes: 3 additions & 4 deletions lib/Kconfig.debug
Original file line number Diff line number Diff line change
Expand Up @@ -978,8 +978,8 @@ config PANIC_TIMEOUT

config SCHED_DEBUG
bool "Collect scheduler debugging info"
depends on DEBUG_KERNEL && PROC_FS
default y
depends on PROC_FS
default n
help
If you say Y here, the /proc/sched_debug file will be provided
that can help debug the scheduler. The runtime overhead of this
Expand All @@ -991,7 +991,7 @@ config SCHED_INFO

config SCHEDSTATS
bool "Collect scheduler statistics"
depends on DEBUG_KERNEL && PROC_FS
depends on PROC_FS
select SCHED_INFO
help
If you say Y here, additional code will be inserted into the
Expand All @@ -1004,7 +1004,6 @@ config SCHEDSTATS

config SCHED_STACK_END_CHECK
bool "Detect stack corruption on calls to schedule()"
depends on DEBUG_KERNEL
default n
help
This option checks for a stack overrun on calls to schedule().
Expand Down