Lines Matching refs:to
11 messages to be added to the output of the syslog() system
15 to /dev/kmsg. This flag just specifies if the timestamp should
25 Selecting this option causes printk() to add a caller "thread id" (if
27 to every message.
30 concurrently call printk() for many times, for it is difficult to
32 line which was divided into multiple lines due to race) came from.
35 no option to enable/disable at the kernel command line parameter or
43 Default loglevel to determine what will be printed on the console.
45 Setting a default here is equivalent to passing in loglevel=<x> in
46 the kernel bootargs. loglevel=<x> continues to override whatever
58 loglevel to use when "quiet" is passed on the kernel commandline.
71 This was hard-coded to KERN_WARNING since at least 2.6.10 but folks
72 that are auditing their logs closely may want to set it to a lower
83 This build option allows you to read kernel boot messages
88 It is likely that you would also need to use "lpj=M" to preset
90 See a previous boot log for the "lpj" value to use for your
94 BOOT_PRINTK_DELAY also may cause LOCKUP_DETECTOR to detect
95 what it believes to be lockup conditions.
177 This adds debug symbols to the kernel and modules (gcc -g), and
178 is needed if you intend to use kernel crashdump or binary object
180 Say Y here only if you plan to debug the kernel.
188 If you say Y here gcc is instructed to generate less debugging
191 be happy. But if you merely need debugging information to
210 to know about the .dwo files and include them.
235 This creates the required links to GDB helper scripts in the
238 additional functions are available to analyze a Linux kernel
246 Enable the __must_check logic in the kernel build. Disable this to
258 Tell gcc to warn at build time for stack frames larger than this.
260 Setting it to 0 disables the warning.
275 Disable some compiler optimizations that tend to generate human unreadable
277 to keep kernel developers who have to stare a lot at assembler listings
283 debugfs is a virtual file system that kernel developers use to put
284 debugging files into. Enable this option to be able to read and
285 write to these files.
293 bool "Install uapi headers to usr/include"
296 This option will install uapi headers (headers exported to user-space)
308 attempt to include files which were not exported, etc.
310 If you're making modifications to header files which are
316 This option determines if the kernel forces gcc to inline the functions
317 developers have marked 'inline'. Doing so takes away freedom from gcc to
321 this algorithm is so good that allowing gcc 4.x and above to make the
323 is there to test gcc for this.
329 references from one section to another section.
338 additional step to occur:
339 - Add the option -fno-inline-functions-called-once to gcc commands.
343 This option tells gcc to inline less (but it does result in
357 # is preferred to always offer frame pointers as a config
377 Add compile-time checks to validate stack metadata, including frame
391 s390 and alpha require percpu variables in modules to be
392 defined weak to work around addressing range issue which
400 option forces all percpu variables to be defined as weak.
410 will be able to flush the buffer cache to disk, reboot the system
424 This may be set to 1 or 0 to enable or disable them all, or
425 to a bitmask as described in Documentation/admin-guide/sysrq.rst.
433 generate some garbage that can lead to spurious false sysrq detects.
434 This option allows you to decide whether you want to enable the
440 Say Y here if you are developing drivers or trying to debug and
448 Say Y here if you need to enable miscellaneous debug code that should
461 kernel to track the life time of various objects and validate
484 timer routines to track the life time of timer objects and
492 work queue routines to track the life time of work objects and
499 Enable this to turn on debugging of RCU list heads (call_rcu() usage).
506 percpu counter routines to track the life time of percpu counter
521 Say Y here to have the kernel do limited verification on memory
522 allocation as well as poisoning memory on free to catch use of freed
532 equivalent to specifying the "slub_debug" parameter on boot.
543 SLUB statistics are useful to debug SLUBs allocation behavior in
544 order find ways to optimize the allocator. This should never be
547 supports the determination of the most active slabs to figure
548 out which slabs are relevant to a particular load.
562 Say Y here if you want to enable the memory leak
564 similar to the Boehm's conservative garbage collector, the
567 feature will introduce an overhead to memory
572 of finding leaks due to the slab objects poisoning.
574 In order to access the kmemleak file, debugfs needs to be
583 Kmemleak must track all the memory allocations to avoid
586 of metadata objects to track such callbacks. After kmemleak is
599 bool "Default kmemleak to off"
602 Say Y here to disable kmemleak by default. It can then be enabled
614 Say N here to disable kmemleak auto scan thread to stop automatic
633 Enable this to turn on extended checks in the virtual-memory system
642 Enable this to turn on VMA caching debug information. Doing so
671 Enable some costly sanity checks in virtual to page code. This can
681 regions to be regularly checked for invalid topology.
699 This option provides the ability to inject artificial errors to
704 notified, write the error code to "actions/<notifier event>/error".
719 bool "Debug access to per_cpu maps"
723 Say Y to verify that the per_cpu map being accessed has
724 been set up. This adds a fair amount of code to kernel memory
743 Say Y here if you want to check for overflows of kernel, IRQ
794 These operands can be used by fuzzing engines to improve the quality
803 then you will want to instrument the whole kernel and you should
805 filesystem fuzzing with AFL) then you will want to enable coverage
812 Enable this to generate a spurious interrupt as soon as a shared
814 Drivers ought to be able to handle interrupts coming in at those
815 points; some don't and need to be caught.
827 Say Y here to enable the kernel to act as a watchdog to detect
830 Softlockups are bugs that cause the kernel to loop in kernel
832 chance to run. The current stack trace is displayed upon
839 Say Y here to enable the kernel to panic on "soft lockups",
840 which are bugs that cause the kernel to loop in kernel
842 sysctl), without giving other tasks a chance to run.
845 to cause the system to reboot automatically after a
864 # Enables a timestamp based low pass filter to compensate for perf based
865 # hard lockup detection which runs too fast due to turbo modes.
871 # arch/ can define HAVE_HARDLOCKUP_DETECTOR_ARCH to provide their own hard
882 Say Y here to enable the kernel to act as a watchdog to detect
885 Hardlockups are bugs that cause the CPU to loop in kernel mode
887 chance to run. The current stack trace is displayed upon detection
894 Say Y here to enable the kernel to panic on "hard lockups",
895 which are bugs that cause the kernel to loop in kernel
913 Say Y here to enable the kernel to detect "hung tasks",
914 which are bugs that cause the task to be stuck in
929 to determine when a task has become non-responsive and should
933 sysctl or by writing a value to
943 Say Y here to enable the kernel to panic on "hung tasks",
944 which are bugs that cause the kernel to leave a task stuck
948 to cause the system to reboot automatically after a
966 Say Y here to enable stall detection on workqueues. If a
978 Say Y here to enable the kernel to panic when it oopses. This
982 This feature is useful to ensure that the kernel does not do
1022 scheduler and related routines to collect statistics about
1025 If you aren't debugging the scheduler or trying to tune a specific
1026 application, you can say N to avoid the very slight overhead
1030 bool "Detect stack corruption on calls to schedule()"
1034 This option checks for a stack overrun on calls to schedule().
1035 If the stack end location is found to be over written always panic as
1037 This is to ensure no erroneous behaviour occurs which could result in
1049 option may have a (very small) performance impact to some
1084 This feature enables the kernel to prove that all locking
1092 In short, this feature enables the kernel to report locking
1096 deadlock scenario would be to trigger: how many
1098 for it to trigger. The proof also does not depend on
1133 If you want to use "perf lock", you also need to turn on
1144 deadlocks (lockups) to be detected and reported automatically.
1151 Say Y here and build SMP to catch missing spinlock initialization
1160 This feature allows mutex semantics violations to be detected and
1185 and unlocks to be detected and reported.
1218 additional runtime checks to debug itself, at the price
1236 Say Y here if you want the kernel to run a short self-test during
1250 after the fact on the running kernel to be tested, if desired.
1253 to be built into the kernel.
1254 Say M if you want these torture tests to build as a module.
1263 It is recommended to enable DEBUG_WW_MUTEX_SLOWPATH in conjunction
1266 Say M if you want these self tests to build as a module.
1274 Enables hooks to interrupt enabling and disabling for
1281 This option causes the kernel to create a /proc/pid/stack for
1290 Some parts of the kernel contain bugs relating to their use of
1292 to generate those numbers securely. This setting ensures that these
1294 occur. This will allow people with obscure setups to know when things
1302 so architecture maintainers really need to do what they can
1303 to get the CRNG seeded sooner after the system is booted.
1304 However, since users cannot do anything actionable to
1308 Say Y here if you want to receive warnings for all uses of
1319 to the syslog.
1327 live on past the point at which a driver decides to drop it's
1328 initial reference to the kobject gained on allocation. An
1337 on the last reference count to improve the visibility of this
1348 Say Y here to make BUG() panics output the file name and line number
1356 Enable this to turn on extended checks in the linked-list
1365 Enable this to turn on extended checks in the priority-ordered
1375 Enable this to turn on checks on scatter-gather tables. This can
1385 Enable this to turn on sanity checking for notifier call chains.
1386 This is most useful for kernel developers to make sure that
1395 Enable this to turn on some debug checking for credential
1397 pointers from task_structs to any given cred struct, and checks to
1402 security pointer in the cred struct is never seen to be invalid.
1413 Workqueue used to implicitly guarantee that work items queued
1417 parameter "workqueue.debug_force_rr_cpu" is added to force
1418 round-robin CPU selection to flush out usages which depend on the
1437 option forces most block device numbers to be allocated from
1438 the extended space and spreads them to discover kernel or
1446 Textual device names (root=/dev/sdXn) will continue to work.
1456 Allows to write steps between "offline" and "online" to the CPUs
1468 This option provides the ability to inject artificial errors to
1469 specified notifier chain callbacks. It is useful to test the error
1479 This option provides the ability to inject artificial errors to
1484 notified, write the error code to "actions/<notifier event>/error".
1502 This option provides the ability to inject artificial errors to
1508 notified, write the error code to "actions/<notifier event>/error".
1519 This option provides the ability to inject artificial errors to
1524 notified, write the error code to "actions/<notifier event>/error".
1597 This will allow you to override a specific function with a return
1599 an error value and have to handle it. This is useful to test the
1608 useful to test the error handling in the mmc block device
1609 and to test how the mmc host driver handles retries from
1633 Enable this option if you want to use the LatencyTOP tool
1634 to find out which userspace is blocking on what kernel operations.
1642 If you want to debug problems which hang or crash the kernel early
1644 this feature to remotely access the memory of the crashed machine
1657 As all changes to the FireWire bus such as enabling and disabling
1659 devices, be sure to have the cable plugged and FireWire enabled on
1680 Choose M here to compile this code as a module. The module will be
1683 Documentation on how to use the module can be found in
1690 Enable this to turn on 'list_sort()' function test. This test is
1720 This option provides a kernel module that can be used to test
1725 Note that if you want to also test saved backtraces, you will
1726 have to enable STACKTRACE as well.
1760 Enable this option to build test module which validates per-cpu
1768 Enable this option to test the atomic64_t functions at boot or
1804 Enable this option to test the bitmap functions at boot.
1811 Enable this option to test the bitfield functions at boot.
1827 Enable this option to test the rhashtable functions at boot.
1834 Enable this option to test the kernel's integer (<linux/hash.h>),
1838 This is intended to help people writing architecture-specific
1848 Enable this option to test priority array manager on boot
1857 Enable this option to test the irq timings code on boot.
1866 on printk when loaded. It is designed to be used for basic
1893 user/kernel boundary testing is working. If it fails to load,
1906 development, but also to run regression tests against changes in
1934 interface for testing firmware loading. This can be used to
1945 This builds the "test_sysctl" module. This driver enables to test the
1946 proc sysctl interfaces available to drivers safely without affecting
1954 This builds the "udelay_test" module that helps to make sure
1978 support to load modules using the Linux kernel's usermode helper.
1997 Test the kernel's ability to detect incorrect calls to
2038 Enable this option to test object aggregation manager on boot
2056 This can be useful to test init_on_alloc and init_on_free features.
2066 to be set.
2071 If you are unsure how to answer this question, answer N.
2093 bool "Filter access to /dev/mem"
2098 If this option is disabled, you allow userspace (root) access to all
2100 access to this is obviously disastrous, but specific access can
2103 use due to the cache aliasing requirements.
2106 file only allows userspace access to PCI space and the BIOS code and
2113 bool "Filter I/O access to /dev/mem"
2116 If this option is disabled, you allow userspace (root) access to all
2118 range. Accidental access to this is obviously disastrous, but
2122 userspace access to *idle* io-memory ranges (see /proc/iomem) This