config PRINTK_TIME	bool "Show timing information on printks"	depends on PRINTK	help	  Selecting this option causes time stamps of the printk()	  messages to be added to the output of the syslog() system	  call and at the console. 	  The timestamp is always recorded internally, and exported	  to /dev/kmsg. This flag just specifies if the timestamp should	  be included, not that the timestamp is recorded. 	  The behavior is also controlled by the kernel command line	  parameter printk.time=1. See Documentation/kernel-parameters.txt config DEFAULT_MESSAGE_LOGLEVEL	int "Default message log level (1-7)"	range 1 7	default "4"	help	  Default log level for printk statements with no specified priority. 	  This was hard-coded to KERN_WARNING since at least 2.6.10 but folks	  that are auditing their logs closely may want to set it to a lower	  priority. config ENABLE_WARN_DEPRECATED	bool "Enable __deprecated logic"	default y	help	  Enable the __deprecated logic in the kernel build.	  Disable this to suppress the "warning: 'foo' is deprecated	  (declared at kernel/power/somefile.c:1234)" messages. config ENABLE_MUST_CHECK	bool "Enable __must_check logic"	default y	help	  Enable the __must_check logic in the kernel build.  Disable this to	  suppress the "warning: ignoring return value of 'foo', declared with	  attribute warn_unused_result" messages. config FRAME_WARN	int "Warn for stack frames larger than (needs gcc 4.4)"	range 0 8192	default 1024 if !64BIT	default 2048 if 64BIT	help	  Tell gcc to warn at build time for stack frames larger than this.	  Setting this too low will cause a lot of warnings.	  Setting it to 0 disables the warning.	  Requires gcc 4.4 config MAGIC_SYSRQ	bool "Magic SysRq key"	depends on !UML	help	  If you say Y here, you will have some control over the system even	  if the system crashes for example during kernel debugging (e.g., you	  will be able to flush the buffer cache to disk, reboot the system	  immediately or dump some status information). This is accomplished	  by pressing various keys while holding SysRq (Alt+PrintScreen). It	  also works on a serial console (on PC hardware at least), if you	  send a BREAK and then within 5 seconds a command keypress. The	  keys are documented in <file:Documentation/sysrq.txt>. Don't say Y	  unless you really know what this hack does. config STRIP_ASM_SYMS	bool "Strip assembler-generated symbols during link"	default n	help	  Strip internal assembler-generated symbols during a link (symbols	  that look like '.Lxxx') so they don't pollute the output of	  get_wchan() and suchlike. config READABLE_ASM        bool "Generate readable assembler code"        depends on DEBUG_KERNEL        help          Disable some compiler optimizations that tend to generate human unreadable          assembler output. This may make the kernel slightly slower, but it helps          to keep kernel developers who have to stare a lot at assembler listings          sane. config UNUSED_SYMBOLS	bool "Enable unused/obsolete exported symbols"	default y if X86	help	  Unused but exported symbols make the kernel needlessly bigger.  For	  that reason most of these unused exports will soon be removed.  This	  option is provided temporarily to provide a transition period in case	  some external kernel module needs one of these symbols anyway. If you	  encounter such a case in your module, consider if you are actually	  using the right API.  (rationale: since nobody in the kernel is using	  this in a module, there is a pretty good chance it's actually the	  wrong interface to use).  If you really need the symbol, please send a	  mail to the linux kernel mailing list mentioning the symbol and why	  you really need it, and what the merge plan to the mainline kernel for	  your module is. config DEBUG_FS	bool "Debug Filesystem"	help	  debugfs is a virtual file system that kernel developers use to put	  debugging files into.  Enable this option to be able to read and	  write to these files. 	  For detailed documentation on the debugfs API, see	  Documentation/DocBook/filesystems. 	  If unsure, say N. config HEADERS_CHECK	bool "Run 'make headers_check' when building vmlinux"	depends on !UML	help	  This option will extract the user-visible kernel headers whenever	  building the kernel, and will run basic sanity checks on them to	  ensure that exported files do not attempt to include files which	  were not exported, etc. 	  If you're making modifications to header files which are	  relevant for userspace, say 'Y', and check the headers	  exported to $(INSTALL_HDR_PATH) (usually 'usr/include' in	  your build tree), to make sure they're suitable. config DEBUG_SECTION_MISMATCH	bool "Enable full Section mismatch analysis"	help	  The section mismatch analysis checks if there are illegal	  references from one section to another section.	  During linktime or runtime, some sections are dropped;	  any use of code/data previously in these sections would	  most likely result in an oops.	  In the code, functions and variables are annotated with	  __init, __devinit, etc. (see the full list in include/linux/init.h),	  which results in the code/data being placed in specific sections.	  The section mismatch analysis is always performed after a full	  kernel build, and enabling this option causes the following	  additional steps to occur:	  - Add the option -fno-inline-functions-called-once to gcc commands.	    When inlining a function annotated with __init in a non-init	    function, we would lose the section information and thus	    the analysis would not catch the illegal reference.	    This option tells gcc to inline less (but it does result in	    a larger kernel).	  - Run the section mismatch analysis for each module/built-in.o file.	    When we run the section mismatch analysis on vmlinux.o, we	    lose valueble information about where the mismatch was	    introduced.	    Running the analysis for each module/built-in.o file	    tells where the mismatch happens much closer to the	    source. The drawback is that the same mismatch is	    reported at least twice.	  - Enable verbose reporting from modpost in order to help resolve	    the section mismatches that are reported. config DEBUG_KERNEL	bool "Kernel debugging"	help	  Say Y here if you are developing drivers or trying to debug and	  identify kernel problems. config DEBUG_SHIRQ	bool "Debug shared IRQ handlers"	depends on DEBUG_KERNEL && GENERIC_HARDIRQS	help	  Enable this to generate a spurious interrupt as soon as a shared	  interrupt handler is registered, and just before one is deregistered.	  Drivers ought to be able to handle interrupts coming in at those	  points; some don't and need to be caught. config LOCKUP_DETECTOR	bool "Detect Hard and Soft Lockups"	depends on DEBUG_KERNEL && !S390	help	  Say Y here to enable the kernel to act as a watchdog to detect	  hard and soft lockups. 	  Softlockups are bugs that cause the kernel to loop in kernel	  mode for more than 20 seconds, without giving other tasks a	  chance to run.  The current stack trace is displayed upon	  detection and the system will stay locked up. 	  Hardlockups are bugs that cause the CPU to loop in kernel mode	  for more than 10 seconds, without letting other interrupts have a	  chance to run.  The current stack trace is displayed upon detection	  and the system will stay locked up. 	  The overhead should be minimal.  A periodic hrtimer runs to	  generate interrupts and kick the watchdog task every 4 seconds.	  An NMI is generated every 10 seconds or so to check for hardlockups. 	  The frequency of hrtimer and NMI events and the soft and hard lockup	  thresholds can be controlled through the sysctl watchdog_thresh. config HARDLOCKUP_DETECTOR	def_bool LOCKUP_DETECTOR && PERF_EVENTS && HAVE_PERF_EVENTS_NMI && \		 !HAVE_NMI_WATCHDOG config BOOTPARAM_HARDLOCKUP_PANIC	bool "Panic (Reboot) On Hard Lockups"	depends on LOCKUP_DETECTOR	help	  Say Y here to enable the kernel to panic on "hard lockups",	  which are bugs that cause the kernel to loop in kernel	  mode with interrupts disabled for more than 10 seconds (configurable	  using the watchdog_thresh sysctl). 	  Say N if unsure. config BOOTPARAM_HARDLOCKUP_PANIC_VALUE	int	depends on LOCKUP_DETECTOR	range 0 1	default 0 if !BOOTPARAM_HARDLOCKUP_PANIC	default 1 if BOOTPARAM_HARDLOCKUP_PANIC config BOOTPARAM_SOFTLOCKUP_PANIC	bool "Panic (Reboot) On Soft Lockups"	depends on LOCKUP_DETECTOR	help	  Say Y here to enable the kernel to panic on "soft lockups",	  which are bugs that cause the kernel to loop in kernel	  mode for more than 20 seconds (configurable using the watchdog_thresh	  sysctl), without giving other tasks a chance to run. 	  The panic can be used in combination with panic_timeout,	  to cause the system to reboot automatically after a	  lockup has been detected. This feature is useful for	  high-availability systems that have uptime guarantees and	  where a lockup must be resolved ASAP. 	  Say N if unsure. config BOOTPARAM_SOFTLOCKUP_PANIC_VALUE	int	depends on LOCKUP_DETECTOR	range 0 1	default 0 if !BOOTPARAM_SOFTLOCKUP_PANIC	default 1 if BOOTPARAM_SOFTLOCKUP_PANIC config PANIC_ON_OOPS	bool "Panic on Oops" if EXPERT	default n	help	  Say Y here to enable the kernel to panic when it oopses. This	  has the same effect as setting oops=panic on the kernel command	  line. 	  This feature is useful to ensure that the kernel does not do	  anything erroneous after an oops which could result in data	  corruption or other issues. 	  Say N if unsure. config PANIC_ON_OOPS_VALUE	int	range 0 1	default 0 if !PANIC_ON_OOPS	default 1 if PANIC_ON_OOPS config DETECT_HUNG_TASK	bool "Detect Hung Tasks"	depends on DEBUG_KERNEL	default LOCKUP_DETECTOR	help	  Say Y here to enable the kernel to detect "hung tasks",	  which are bugs that cause the task to be stuck in	  uninterruptible "D" state indefinitiley. 	  When a hung task is detected, the kernel will print the	  current stack trace (which you should report), but the	  task will stay in uninterruptible state. If lockdep is	  enabled then all held locks will also be reported. This	  feature has negligible overhead. config DEFAULT_HUNG_TASK_TIMEOUT	int "Default timeout for hung task detection (in seconds)"	depends on DETECT_HUNG_TASK	default 120	help	  This option controls the default timeout (in seconds) used	  to determine when a task has become non-responsive and should	  be considered hung. 	  It can be adjusted at runtime via the kernel.hung_task_timeout_secs	  sysctl or by writing a value to	  /proc/sys/kernel/hung_task_timeout_secs. 	  A timeout of 0 disables the check.  The default is two minutes.	  Keeping the default should be fine in most cases. config BOOTPARAM_HUNG_TASK_PANIC	bool "Panic (Reboot) On Hung Tasks"	depends on DETECT_HUNG_TASK	help	  Say Y here to enable the kernel to panic on "hung tasks",	  which are bugs that cause the kernel to leave a task stuck	  in uninterruptible "D" state. 	  The panic can be used in combination with panic_timeout,	  to cause the system to reboot automatically after a	  hung task has been detected. This feature is useful for	  high-availability systems that have uptime guarantees and	  where a hung tasks must be resolved ASAP. 	  Say N if unsure. config BOOTPARAM_HUNG_TASK_PANIC_VALUE	int	depends on DETECT_HUNG_TASK	range 0 1	default 0 if !BOOTPARAM_HUNG_TASK_PANIC	default 1 if BOOTPARAM_HUNG_TASK_PANIC config SCHED_DEBUG	bool "Collect scheduler debugging info"	depends on DEBUG_KERNEL && PROC_FS	default y	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	  option is minimal. config SCHEDSTATS	bool "Collect scheduler statistics"	depends on DEBUG_KERNEL && PROC_FS	help	  If you say Y here, additional code will be inserted into the	  scheduler and related routines to collect statistics about	  scheduler behavior and provide them in /proc/schedstat.  These	  stats may be useful for both tuning and debugging the scheduler	  If you aren't debugging the scheduler or trying to tune a specific	  application, you can say N to avoid the very slight overhead	  this adds. config TIMER_STATS	bool "Collect kernel timers statistics"	depends on DEBUG_KERNEL && PROC_FS	help	  If you say Y here, additional code will be inserted into the	  timer routines to collect statistics about kernel timers being	  reprogrammed. The statistics can be read from /proc/timer_stats.	  The statistics collection is started by writing 1 to /proc/timer_stats,	  writing 0 stops it. This feature is useful to collect information	  about timer usage patterns in kernel and userspace. This feature	  is lightweight if enabled in the kernel config but not activated	  (it defaults to deactivated on bootup and will only be activated	  if some application like powertop activates it explicitly). config DEBUG_OBJECTS	bool "Debug object operations"	depends on DEBUG_KERNEL	help	  If you say Y here, additional code will be inserted into the	  kernel to track the life time of various objects and validate	  the operations on those objects. config DEBUG_OBJECTS_SELFTEST	bool "Debug objects selftest"	depends on DEBUG_OBJECTS	help	  This enables the selftest of the object debug code. config DEBUG_OBJECTS_FREE	bool "Debug objects in freed memory"	depends on DEBUG_OBJECTS	help	  This enables checks whether a k/v free operation frees an area	  which contains an object which has not been deactivated	  properly. This can make kmalloc/kfree-intensive workloads	  much slower. config DEBUG_OBJECTS_TIMERS	bool "Debug timer objects"	depends on DEBUG_OBJECTS	help	  If you say Y here, additional code will be inserted into the	  timer routines to track the life time of timer objects and	  validate the timer operations. config DEBUG_OBJECTS_WORK	bool "Debug work objects"	depends on DEBUG_OBJECTS	help	  If you say Y here, additional code will be inserted into the	  work queue routines to track the life time of work objects and	  validate the work operations. config DEBUG_OBJECTS_RCU_HEAD	bool "Debug RCU callbacks objects"	depends on DEBUG_OBJECTS	help	  Enable this to turn on debugging of RCU list heads (call_rcu() usage). config DEBUG_OBJECTS_PERCPU_COUNTER	bool "Debug percpu counter objects"	depends on DEBUG_OBJECTS	help	  If you say Y here, additional code will be inserted into the	  percpu counter routines to track the life time of percpu counter	  objects and validate the percpu counter operations. config DEBUG_OBJECTS_ENABLE_DEFAULT	int "debug_objects bootup default value (0-1)"        range 0 1        default "1"        depends on DEBUG_OBJECTS        help          Debug objects boot parameter default value config DEBUG_SLAB	bool "Debug slab memory allocations"	depends on DEBUG_KERNEL && SLAB && !KMEMCHECK	help	  Say Y here to have the kernel do limited verification on memory	  allocation as well as poisoning memory on free to catch use of freed	  memory. This can make kmalloc/kfree-intensive workloads much slower. config DEBUG_SLAB_LEAK	bool "Memory leak debugging"	depends on DEBUG_SLAB config SLUB_DEBUG_ON	bool "SLUB debugging on by default"	depends on SLUB && SLUB_DEBUG && !KMEMCHECK	default n	help	  Boot with debugging on by default. SLUB boots by default with	  the runtime debug capabilities switched off. Enabling this is	  equivalent to specifying the "slub_debug" parameter on boot.	  There is no support for more fine grained debug control like	  possible with slub_debug=xxx. SLUB debugging may be switched	  off in a kernel built with CONFIG_SLUB_DEBUG_ON by specifying	  "slub_debug=-". config SLUB_STATS	default n	bool "Enable SLUB performance statistics"	depends on SLUB && SYSFS	help	  SLUB statistics are useful to debug SLUBs allocation behavior in	  order find ways to optimize the allocator. This should never be	  enabled for production use since keeping statistics slows down	  the allocator by a few percentage points. The slabinfo command	  supports the determination of the most active slabs to figure	  out which slabs are relevant to a particular load.	  Try running: slabinfo -DA config DEBUG_KMEMLEAK	bool "Kernel memory leak detector"	depends on DEBUG_KERNEL && EXPERIMENTAL && \		(X86 || ARM || PPC || MIPS || S390 || SPARC64 || SUPERH || MICROBLAZE || TILE) 	select DEBUG_FS	select STACKTRACE if STACKTRACE_SUPPORT	select KALLSYMS	select CRC32	help	  Say Y here if you want to enable the memory leak	  detector. The memory allocation/freeing is traced in a way	  similar to the Boehm's conservative garbage collector, the	  difference being that the orphan objects are not freed but	  only shown in /sys/kernel/debug/kmemleak. Enabling this	  feature will introduce an overhead to memory	  allocations. See Documentation/kmemleak.txt for more	  details. 	  Enabling DEBUG_SLAB or SLUB_DEBUG may increase the chances	  of finding leaks due to the slab objects poisoning. 	  In order to access the kmemleak file, debugfs needs to be	  mounted (usually at /sys/kernel/debug). config DEBUG_KMEMLEAK_EARLY_LOG_SIZE	int "Maximum kmemleak early log entries"	depends on DEBUG_KMEMLEAK	range 200 40000	default 400	help	  Kmemleak must track all the memory allocations to avoid	  reporting false positives. Since memory may be allocated or	  freed before kmemleak is initialised, an early log buffer is	  used to store these actions. If kmemleak reports "early log	  buffer exceeded", please increase this value. config DEBUG_KMEMLEAK_TEST	tristate "Simple test for the kernel memory leak detector"	depends on DEBUG_KMEMLEAK && m	help	  This option enables a module that explicitly leaks memory. 	  If unsure, say N. config DEBUG_KMEMLEAK_DEFAULT_OFF	bool "Default kmemleak to off"	depends on DEBUG_KMEMLEAK	help

Lines 1–500 of 1424. Load more