Lines Matching refs:in
35 specified in milliseconds on the kernel command line,
58 implicitly compiles in all pr_debug() and dev_dbg() calls, which
62 pr_debug() calls in it are enabled by default, but can be
69 which is contained in the 'debugfs' filesystem. Thus, the debugfs
98 // enable all the messages in file svcsock.c
102 // enable all the messages in the NFS server module
106 // enable all 12 messages in the function svc_process()
110 // disable all 12 messages in the function svc_process()
125 debugging info resulting in a larger kernel image.
147 bool "Produce split debuginfo in .dwo files"
152 because it stores the information only once on disk in .dwo
153 files instead of multiple times in object files and executables.
168 variables in gdb on optimized code.
174 This creates the required links to GDB helper scripts in the
185 Enable the __deprecated logic in the kernel build.
193 Enable the __must_check logic in the kernel build. Disable this to
232 option is provided temporarily to provide a transition period in case
234 encounter such a case in your module, consider if you are actually
235 using the right API. (rationale: since nobody in the kernel is using
236 this in a module, there is a pretty good chance it's actually the
252 feature on your build, it is disabled in default. You should pass
253 "page_owner=on" to boot parameter in order to enable it. Eats
283 exported to $(INSTALL_HDR_PATH) (usually 'usr/include' in
292 any use of code/data previously in these sections would
293 most likely result in an oops.
295 __init,, etc. (see the full list in include/linux/init.h),
296 which results in the code/data being placed in specific sections.
301 When inlining a function annotated with __init in a non-init
304 This option tells gcc to inline less (but it does result in
306 - Run the section mismatch analysis for each module/built-in.o file.
310 Running the analysis for each module/built-in.o file
314 - Enable verbose reporting from modpost in order to help resolve
345 in case of kernel bugs. (precise oopses/stacktraces/warnings)
363 s390 and alpha require percpu variables in modules to be
387 keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
397 to a bitmask as described in Documentation/sysrq.txt.
424 bool "Debug objects in freed memory"
492 off in a kernel built with CONFIG_SLUB_DEBUG_ON by specifying
500 SLUB statistics are useful to debug SLUBs allocation behavior in
520 detector. The memory allocation/freeing is traced in a way
523 only shown in /sys/kernel/debug/kmemleak. Enabling this
566 task has ever had available in the sysrq-T and sysrq-P debug output.
574 Enable this to turn on extended checks in the virtual-memory system
584 can cause significant overhead, so only enable it in non-production
609 Enable some costly sanity checks in virtual to page code. This can
686 These kinds of bugs usually occur when call-chains in the
690 Use this in cases where you see apparently random memory
691 corruption, especially if it appears in 'struct thread_info'
693 If in doubt, say "N".
715 KCOV exposes kernel code coverage information in a form suitable
741 Drivers ought to be able to handle interrupts coming in at those
753 Softlockups are bugs that cause the kernel to loop in kernel
758 Hardlockups are bugs that cause the CPU to loop in kernel mode
780 which are bugs that cause the kernel to loop in kernel
798 which are bugs that cause the kernel to loop in kernel
802 The panic can be used in combination with panic_timeout,
823 which are bugs that cause the task to be stuck in
828 task will stay in uninterruptible state. If lockdep is
833 int "Default timeout for hung task detection (in seconds)"
837 This option controls the default timeout (in seconds) used
846 Keeping the default should be fine in most cases.
854 in uninterruptible "D" state.
856 The panic can be used in combination with panic_timeout,
892 anything erroneous after an oops which could result in data
907 Set the timeout value (in seconds) until a reboot occurs when the
941 scheduler behavior and provide them in /proc/schedstat. These
955 This is to ensure no erroneous behaviour occurs which could result in
966 This may include checks in the timekeeping hotpaths, so this
981 about timer usage patterns in kernel and userspace. This feature
982 is lightweight if enabled in the kernel config but not activated
993 if kernel code uses it in a preemption-unsafe way. Also, the kernel
1012 best used in conjunction with the NMI watchdog so that spinlock
1035 it really should not be enabled in a production or distro kernel,
1064 that occurs in the kernel runtime is mathematically
1089 and rwsems - in which case all dependencies between these
1231 Enable this to turn on extended checks in the linked-list
1240 Enable this to turn on extended checks in the priority-ordered
1277 security pointer in the cred struct is never seen to be invalid.
1361 involving grace-period pre-initialization, in other words, it
1364 of CPUs. This is useful when torture-testing RCU, but in
1386 grace-period initialization, in other words, it makes your
1389 This is useful when torture-testing RCU, but in almost no
1411 cleanup, in other words, it makes your kernel less stable.
1414 torture-testing RCU, but in almost no other circumstance.
1429 int "RCU CPU stall timeout in seconds"
1444 This option provides tracing in RCU which presents stats
1445 in debugfs for debugging RCU implementation.
1454 This option provides consistency checks in RCU's handling of
1455 NO_HZ. These checks have proven quite helpful in detecting
1456 bugs in arch-specific NO_HZ code.
1660 useful to test the error handling in the mmc block device
1717 Documentation on how to use the module can be found in
1800 tristate "Test functions located in the hexdump module at runtime"
1803 tristate "Test functions located in the string_helpers module at runtime"
1820 tristate "Test functions located in the uuid module at runtime"
1860 all OHCI1394 controllers which are found in the PCI config space.
1868 in charge of the OHCI-1394 controllers should be used instead.
1877 With this option you will be able to detect common bugs in device
1882 accessed by the cpu in a way that could cause data corruption. For
1913 a regression has been detected in the user/kernel memory boundary
1925 current setting. This is in particular useful for BPF JIT compiler
1926 development, but also to run regression tests against changes in
1994 enabled, even in this case there are restrictions on /dev/mem
2002 If in doubt, say Y.
2018 If in doubt, say Y.