Kconfig.debug 1.3 KB

12345678910111213141516171819202122232425262728293031323334353637383940
  1. menu "Kernel hacking"
  2. config TRACE_IRQFLAGS_SUPPORT
  3. bool
  4. default y
  5. source "lib/Kconfig.debug"
  6. config DEBUG_STACKOVERFLOW
  7. bool "Check for stack overflows"
  8. depends on DEBUG_KERNEL
  9. help
  10. This option will cause messages to be printed if free stack space
  11. drops below a certain limit.
  12. config 4KSTACKS
  13. bool "Use 4Kb for kernel stacks instead of 8Kb"
  14. depends on DEBUG_KERNEL
  15. help
  16. If you say Y here the kernel will use a 4Kb stacksize for the
  17. kernel stack attached to each process/thread. This facilitates
  18. running more threads on a system and also reduces the pressure
  19. on the VM subsystem for higher order allocations. This option
  20. will also use IRQ stacks to compensate for the reduced stackspace.
  21. config METAG_FUNCTION_TRACE
  22. bool "Output Meta real-time trace data for function entry/exit"
  23. help
  24. If you say Y here the kernel will use the Meta hardware trace
  25. unit to output information about function entry and exit that
  26. can be used by a debugger for profiling and call-graphs.
  27. config METAG_POISON_CATCH_BUFFERS
  28. bool "Poison catch buffer contents on kernel entry"
  29. help
  30. If you say Y here the kernel will write poison data to the
  31. catch buffer registers on kernel entry. This will make any
  32. problem with catch buffer handling much more apparent.
  33. endmenu