Kconfig.debug 3.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102
  1. config DRM_I915_WERROR
  2. bool "Force GCC to throw an error instead of a warning when compiling"
  3. # As this may inadvertently break the build, only allow the user
  4. # to shoot oneself in the foot iff they aim really hard
  5. depends on EXPERT
  6. # We use the dependency on !COMPILE_TEST to not be enabled in
  7. # allmodconfig or allyesconfig configurations
  8. depends on !COMPILE_TEST
  9. default n
  10. help
  11. Add -Werror to the build flags for (and only for) i915.ko.
  12. Do not enable this unless you are writing code for the i915.ko module.
  13. Recommended for driver developers only.
  14. If in doubt, say "N".
  15. config DRM_I915_DEBUG
  16. bool "Enable additional driver debugging"
  17. depends on DRM_I915
  18. select PREEMPT_COUNT
  19. select I2C_CHARDEV
  20. select DRM_DP_AUX_CHARDEV
  21. select X86_MSR # used by igt/pm_rpm
  22. select DRM_VGEM # used by igt/prime_vgem (dmabuf interop checks)
  23. select DRM_DEBUG_MM if DRM=y
  24. select DRM_DEBUG_MM_SELFTEST
  25. select DRM_I915_SW_FENCE_DEBUG_OBJECTS
  26. select DRM_I915_SELFTEST
  27. default n
  28. help
  29. Choose this option to turn on extra driver debugging that may affect
  30. performance but will catch some internal issues.
  31. Recommended for driver developers only.
  32. If in doubt, say "N".
  33. config DRM_I915_DEBUG_GEM
  34. bool "Insert extra checks into the GEM internals"
  35. default n
  36. depends on DRM_I915_WERROR
  37. help
  38. Enable extra sanity checks (including BUGs) along the GEM driver
  39. paths that may slow the system down and if hit hang the machine.
  40. Recommended for driver developers only.
  41. If in doubt, say "N".
  42. config DRM_I915_SW_FENCE_DEBUG_OBJECTS
  43. bool "Enable additional driver debugging for fence objects"
  44. depends on DRM_I915
  45. select DEBUG_OBJECTS
  46. default n
  47. help
  48. Choose this option to turn on extra driver debugging that may affect
  49. performance but will catch some internal issues.
  50. Recommended for driver developers only.
  51. If in doubt, say "N".
  52. config DRM_I915_SELFTEST
  53. bool "Enable selftests upon driver load"
  54. depends on DRM_I915
  55. default n
  56. select FAULT_INJECTION
  57. select PRIME_NUMBERS
  58. help
  59. Choose this option to allow the driver to perform selftests upon
  60. loading; also requires the i915.selftest=1 module parameter. To
  61. exit the module after running the selftests (i.e. to prevent normal
  62. module initialisation afterwards) use i915.selftest=-1.
  63. Recommended for driver developers only.
  64. If in doubt, say "N".
  65. config DRM_I915_LOW_LEVEL_TRACEPOINTS
  66. bool "Enable low level request tracing events"
  67. depends on DRM_I915
  68. default n
  69. help
  70. Choose this option to turn on low level request tracing events.
  71. This provides the ability to precisely monitor engine utilisation
  72. and also analyze the request dependency resolving timeline.
  73. If in doubt, say "N".
  74. config DRM_I915_DEBUG_VBLANK_EVADE
  75. bool "Enable extra debug warnings for vblank evasion"
  76. depends on DRM_I915
  77. default n
  78. help
  79. Choose this option to turn on extra debug warnings for the
  80. vblank evade mechanism. This gives a warning every time the
  81. the deadline allotted for the vblank evade critical section
  82. is exceeded, even if there isn't an actual risk of missing
  83. the vblank.
  84. If in doubt, say "N".