Lines Matching refs:in
26 in task context) or a caller "processor id" (if not in task context)
45 Setting a default here is equivalent to passing in loglevel=<x> in
50 usage in the kernel. That is controlled by the MESSAGE_LOGLEVEL_DEFAULT
76 by default. To change that, use loglevel=<x> in the kernel bootargs,
85 specified in milliseconds on the kernel command line,
108 implicitly compiles in all pr_debug() and dev_dbg() calls, which
112 pr_debug() calls in it are enabled by default, but can be
119 which is contained in the 'debugfs' filesystem. Thus, the debugfs
148 // enable all the messages in file svcsock.c
152 // enable all the messages in the NFS server module
156 // enable all 12 messages in the function svc_process()
160 // disable all 12 messages in the function svc_process()
176 debugging info resulting in a larger kernel image.
198 bool "Produce split debuginfo in .dwo files"
204 because it stores the information only once on disk in .dwo
205 files instead of multiple times in object files and executables.
221 variables in gdb on optimized code.
235 This creates the required links to GDB helper scripts in the
246 Enable the __must_check logic in the kernel build. Disable this to
322 decision will become the default in the future. Until then this option
331 any use of code/data previously in these sections would
332 most likely result in an oops.
334 __init,, etc. (see the full list in include/linux/init.h),
335 which results in the code/data being placed in specific sections.
340 When inlining a function annotated with __init in a non-init
343 This option tells gcc to inline less (but it does result in
370 in case of kernel bugs. (precise oopses/stacktraces/warnings)
391 s390 and alpha require percpu variables in modules to be
415 keys are documented in <file:Documentation/admin-guide/sysrq.rst>.
425 to a bitmask as described in Documentation/admin-guide/sysrq.rst.
471 bool "Debug objects in freed memory"
535 off in a kernel built with CONFIG_SLUB_DEBUG_ON by specifying
543 SLUB statistics are useful to debug SLUBs allocation behavior in
563 detector. The memory allocation/freeing is traced in a way
566 only shown in /sys/kernel/debug/kmemleak. Enabling this
625 task has ever had available in the sysrq-T and sysrq-P debug output.
633 Enable this to turn on extended checks in the virtual-memory system
643 can cause significant overhead, so only enable it in non-production
671 Enable some costly sanity checks in virtual to page code. This can
748 These kinds of bugs usually occur when call-chains in the
752 Use this in cases where you see apparently random memory
753 corruption, especially if it appears in 'struct thread_info'
755 If in doubt, say "N".
778 KCOV exposes kernel code coverage information in a form suitable
792 KCOV also exposes operands of every comparison in the instrumented
814 Drivers ought to be able to handle interrupts coming in at those
830 Softlockups are bugs that cause the kernel to loop in kernel
840 which are bugs that cause the kernel to loop in kernel
844 The panic can be used in combination with panic_timeout,
885 Hardlockups are bugs that cause the CPU to loop in kernel mode
895 which are bugs that cause the kernel to loop in kernel
914 which are bugs that cause the task to be stuck in
919 task will stay in uninterruptible state. If lockdep is
924 int "Default timeout for hung task detection (in seconds)"
928 This option controls the default timeout (in seconds) used
937 Keeping the default should be fine in most cases.
945 in uninterruptible "D" state.
947 The panic can be used in combination with panic_timeout,
983 anything erroneous after an oops which could result in data
998 Set the timeout value (in seconds) until a reboot occurs when the
1023 scheduler behavior and provide them in /proc/schedstat. These
1037 This is to ensure no erroneous behaviour occurs which could result in
1048 This may include checks in the timekeeping hotpaths, so this
1061 if kernel code uses it in a preemption-unsafe way. Also, the kernel
1085 that occurs in the kernel runtime is mathematically
1110 and rwsems - in which case all dependencies between these
1153 best used in conjunction with the NMI watchdog so that spinlock
1176 it really should not be enabled in a production or distro kernel,
1263 It is recommended to enable DEBUG_WW_MUTEX_SLOWPATH in conjunction
1300 result in dmesg getting spammed for a surprisingly long
1310 those developers interested in improving the security of
1356 Enable this to turn on extended checks in the linked-list
1365 Enable this to turn on extended checks in the priority-ordered
1402 security pointer in the cred struct is never seen to be invalid.
1600 error handling in various subsystems.
1608 useful to test the error handling in the mmc block device
1655 all OHCI1394 controllers which are found in the PCI config space.
1663 in charge of the OHCI-1394 controllers should be used instead.
1683 Documentation on how to use the module can be found in
1787 tristate "Test functions located in the hexdump module at runtime"
1790 tristate "Test functions located in the string_helpers module at runtime"
1816 tristate "Test functions located in the uuid module at runtime"
1894 a regression has been detected in the user/kernel memory boundary
1905 current setting. This is in particular useful for BPF JIT compiler
1906 development, but also to run regression tests against changes in
2019 load test modules that will be livepatched in various scenarios.
2078 data corruption in kernel memory structures when they get checked
2102 enabled, even in this case there are restrictions on /dev/mem
2110 If in doubt, say Y.
2126 If in doubt, say Y.