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
251 feature on your build, it is disabled in default. You should pass
252 "page_owner=on" to boot parameter in order to enable it. Eats
281 exported to $(INSTALL_HDR_PATH) (usually 'usr/include' in
290 any use of code/data previously in these sections would
291 most likely result in an oops.
293 __init,, etc. (see the full list in include/linux/init.h),
294 which results in the code/data being placed in specific sections.
299 When inlining a function annotated with __init in a non-init
302 This option tells gcc to inline less (but it does result in
304 - Run the section mismatch analysis for each module/built-in.o file.
308 Running the analysis for each module/built-in.o file
312 - Enable verbose reporting from modpost in order to help resolve
343 in case of kernel bugs. (precise oopses/stacktraces/warnings)
349 s390 and alpha require percpu variables in modules to be
373 keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
383 to a bitmask as described in Documentation/sysrq.txt.
410 bool "Debug objects in freed memory"
478 off in a kernel built with CONFIG_SLUB_DEBUG_ON by specifying
486 SLUB statistics are useful to debug SLUBs allocation behavior in
506 detector. The memory allocation/freeing is traced in a way
509 only shown in /sys/kernel/debug/kmemleak. Enabling this
552 task has ever had available in the sysrq-T and sysrq-P debug output.
560 Enable this to turn on extended checks in the virtual-memory system
570 can cause significant overhead, so only enable it in non-production
587 Enable some costly sanity checks in virtual to page code. This can
664 These kinds of bugs usually occur when call-chains in the
668 Use this in cases where you see apparently random memory
669 corruption, especially if it appears in 'struct thread_info'
671 If in doubt, say "N".
691 KCOV exposes kernel code coverage information in a form suitable
706 Drivers ought to be able to handle interrupts coming in at those
718 Softlockups are bugs that cause the kernel to loop in kernel
723 Hardlockups are bugs that cause the CPU to loop in kernel mode
757 which are bugs that cause the kernel to loop in kernel
775 which are bugs that cause the kernel to loop in kernel
779 The panic can be used in combination with panic_timeout,
800 which are bugs that cause the task to be stuck in
805 task will stay in uninterruptible state. If lockdep is
810 int "Default timeout for hung task detection (in seconds)"
814 This option controls the default timeout (in seconds) used
823 Keeping the default should be fine in most cases.
831 in uninterruptible "D" state.
833 The panic can be used in combination with panic_timeout,
858 anything erroneous after an oops which could result in data
873 Set the timeout value (in seconds) until a reboot occurs when the
907 scheduler behavior and provide them in /proc/schedstat. These
921 This is to ensure no erroneous behaviour occurs which could result in
932 This may include checks in the timekeeping hotpaths, so this
947 about timer usage patterns in kernel and userspace. This feature
948 is lightweight if enabled in the kernel config but not activated
959 if kernel code uses it in a preemption-unsafe way. Also, the kernel
978 best used in conjunction with the NMI watchdog so that spinlock
1001 it really should not be enabled in a production or distro kernel,
1030 that occurs in the kernel runtime is mathematically
1055 and rwsems - in which case all dependencies between these
1194 Enable this to turn on extended checks in the linked-list
1203 Enable this to turn on extended checks in the priority-ordered
1240 security pointer in the cred struct is never seen to be invalid.
1324 involving grace-period pre-initialization, in other words, it
1327 of CPUs. This is useful when torture-testing RCU, but in
1349 grace-period initialization, in other words, it makes your
1352 This is useful when torture-testing RCU, but in almost no
1374 cleanup, in other words, it makes your kernel less stable.
1377 torture-testing RCU, but in almost no other circumstance.
1392 int "RCU CPU stall timeout in seconds"
1407 This option provides tracing in RCU which presents stats
1408 in debugfs for debugging RCU implementation.
1417 This option provides consistency checks in RCU's handling of
1418 NO_HZ. These checks have proven quite helpful in detecting
1419 bugs in arch-specific NO_HZ code.
1573 useful to test the error handling in the mmc block device
1649 Documentation on how to use the module can be found in
1732 tristate "Test functions located in the hexdump module at runtime"
1735 tristate "Test functions located in the string_helpers module at runtime"
1780 all OHCI1394 controllers which are found in the PCI config space.
1788 in charge of the OHCI-1394 controllers should be used instead.
1793 bool "Build targets in Documentation/ tree"
1796 This option attempts to build objects from the source files in the
1806 With this option you will be able to detect common bugs in device
1811 accessed by the cpu in a way that could cause data corruption. For
1842 a regression has been detected in the user/kernel memory boundary
1854 current setting. This is in particular useful for BPF JIT compiler
1855 development, but also to run regression tests against changes in