Lines Matching refs:be
8 messages to be added to the output of the syslog() system
13 be included, not that the timestamp is recorded.
45 what it believes to be lockup conditions.
55 otherwise be available at runtime. These messages can then be
62 pr_debug() calls in it are enabled by default, but can be
70 filesystem must first be mounted before making use of this feature.
72 file contains a list of the debug statements that can be enabled. The
140 be happy. But if you merely need debugging information to
176 scripts will be automatically imported by gdb as well, and
231 that reason most of these unused exports will soon be removed. This
264 debugging files into. Enable this option to be able to read and
343 If you say Y here the resulting kernel image will be slightly
363 s390 and alpha require percpu variables in modules to be
368 1. percpu symbols must be unique whether static or not
369 2. percpu variables can't be defined inside a function
372 option forces all percpu variables to be defined as weak.
382 will be able to flush the buffer cache to disk, reboot the system
396 This may be set to 1 or 0 to enable or disable them all, or
413 If you say Y here, additional code will be inserted into the
436 If you say Y here, additional code will be inserted into the
444 If you say Y here, additional code will be inserted into the
458 If you say Y here, additional code will be inserted into the
491 possible with slub_debug=xxx. SLUB debugging may be switched
501 order find ways to optimize the allocator. This should never be
531 In order to access the kmemleak file, debugfs needs to be
541 reporting false positives. Since memory may be allocated or
558 Say Y here to disable kmemleak by default. It can then be enabled
619 regions to be regularly checked for invalid topology.
628 information will be printed at KERN_DEBUG loglevel depending
641 If the notifier call chain should be failed with some events
652 be called memory-notifier-error-inject.
718 If RANDOMIZE_BASE is enabled, PC values will not be stable across
741 Drivers ought to be able to handle interrupts coming in at those
742 points; some don't and need to be caught.
763 The overhead should be minimal. A periodic hrtimer runs to
768 thresholds can be controlled through the sysctl watchdog_thresh.
802 The panic can be used in combination with panic_timeout,
806 where a lockup must be resolved ASAP.
823 which are bugs that cause the task to be stuck in
829 enabled then all held locks will also be reported. This
839 be considered hung.
841 It can be adjusted at runtime via the kernel.hung_task_timeout_secs
846 Keeping the default should be fine in most cases.
856 The panic can be used in combination with panic_timeout,
860 where a hung tasks must be resolved ASAP.
879 state. This can be configured through kernel parameter
917 If you say Y here, the /proc/sched_debug file will be provided
929 runqueue is throttled. This may be useful for detecting
939 If you say Y here, additional code will be inserted into the
942 stats may be useful for both tuning and debugging the scheduler
953 If the stack end location is found to be over written always panic as
954 the content of the corrupted region can no longer be trusted.
963 which may be helpful when diagnosing issues where timekeeping
976 If you say Y here, additional code will be inserted into the
978 reprogrammed. The statistics can be read from /proc/timer_stats.
983 (it defaults to deactivated on bootup and will only be activated
1003 deadlocks (lockups) to be detected and reported automatically.
1019 This feature allows mutex semantics violations to be detected and
1035 it really should not be enabled in a production or distro kernel,
1075 deadlock scenario would be to trigger: how many
1076 participant CPUs, tasks and irq-contexts would be needed
1080 is), it will be proven so and will immediately be
1088 NOTE: this feature can also be enabled for rwlocks, mutexes
1153 lock debugging then those bugs wont be detected of course.)
1164 on kernel locking primitives. The kernel module may be built
1165 after the fact on the running kernel to be tested, if desired.
1168 to be built into the kernel.
1193 If you say Y here, some extra kobject debugging messages will be sent
1204 example of this would be a struct device which has just been
1208 the memory backing the kobject can be immediately freed. This
1277 security pointer in the cred struct is never seen to be invalid.
1293 disabling, allowing multiple RCU-lockdep warnings to be printed
1306 to flag any non-RCU used of annotated pointers. This can be
1328 tests on the RCU infrastructure. The kernel module may be built
1329 after the fact on the running kernel to be tested, if desired.
1331 Say Y here if you want RCU performance tests to be built into
1345 on the RCU infrastructure. The kernel module may be built
1346 after the fact on the running kernel to be tested, if desired.
1348 Say Y here if you want RCU torture tests to be built into
1471 preferred work items may be put on foreign CPUs. Kernel
1476 be impacted.
1492 option forces most block device numbers to be allocated from
1512 sysfs target file so states can be stepped granular. This is a debug
1513 option for now as the hotplug machinery cannot be stopped and
1533 This option provides a kernel module that can be used to test
1538 If the notifier call chain should be failed with some events
1549 be called cpu-notifier-error-inject.
1562 If the notifier call chain should be failed with some events
1573 be called pm-notifier-error-inject.
1586 If the notifier call chain should be failed with some events
1590 be called of-reconfig-notifier-error-inject.
1602 If the notifier call chain should be failed with some events
1613 be called netdev-notifier-error-inject.
1714 Choose M here to compile this code as a module. The module will be
1717 Documentation on how to use the module can be found in
1746 This option provides a kernel module that can be used to test
1864 devices, be sure to have the cable plugged and FireWire enabled on
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
1897 on printk when loaded. It is designed to be used for basic
1900 and will not normally be loaded by the system unless explicitly
1938 interface for testing firmware loading. This can be used to
1940 actual firmware-using device. The contents can be rechecked by
1959 to be set.
1993 be used by people debugging the kernel. Note that with PAT support
2011 specific access can be used by people debugging kernel drivers.
2016 if the driver using a given range cannot be disabled.