Kconfig.debug 5.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157
  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 DEBUG_FS
  19. select PREEMPT_COUNT
  20. select I2C_CHARDEV
  21. select DRM_DP_AUX_CHARDEV
  22. select X86_MSR # used by igt/pm_rpm
  23. select DRM_VGEM # used by igt/prime_vgem (dmabuf interop checks)
  24. select DRM_DEBUG_MM if DRM=y
  25. select STACKDEPOT if DRM=y # for DRM_DEBUG_MM
  26. select DRM_DEBUG_SELFTEST
  27. select SW_SYNC # signaling validation framework (igt/syncobj*)
  28. select DRM_I915_SW_FENCE_DEBUG_OBJECTS
  29. select DRM_I915_SELFTEST
  30. default n
  31. help
  32. Choose this option to turn on extra driver debugging that may affect
  33. performance but will catch some internal issues.
  34. Recommended for driver developers only.
  35. If in doubt, say "N".
  36. config DRM_I915_DEBUG_GEM
  37. bool "Insert extra checks into the GEM internals"
  38. default n
  39. depends on DRM_I915_WERROR
  40. help
  41. Enable extra sanity checks (including BUGs) along the GEM driver
  42. paths that may slow the system down and if hit hang the machine.
  43. Recommended for driver developers only.
  44. If in doubt, say "N".
  45. config DRM_I915_TRACE_GEM
  46. bool "Insert extra ftrace output from the GEM internals"
  47. depends on DRM_I915_DEBUG_GEM
  48. select TRACING
  49. default n
  50. help
  51. Enable additional and verbose debugging output that will spam
  52. ordinary tests, but may be vital for post-mortem debugging when
  53. used with /proc/sys/kernel/ftrace_dump_on_oops
  54. Recommended for driver developers only.
  55. If in doubt, say "N".
  56. config DRM_I915_SW_FENCE_DEBUG_OBJECTS
  57. bool "Enable additional driver debugging for fence objects"
  58. depends on DRM_I915
  59. select DEBUG_OBJECTS
  60. default n
  61. help
  62. Choose this option to turn on extra driver debugging that may affect
  63. performance but will catch some internal issues.
  64. Recommended for driver developers only.
  65. If in doubt, say "N".
  66. config DRM_I915_SW_FENCE_CHECK_DAG
  67. bool "Enable additional driver debugging for detecting dependency cycles"
  68. depends on DRM_I915
  69. default n
  70. help
  71. Choose this option to turn on extra driver debugging that may affect
  72. performance but will catch some internal issues.
  73. Recommended for driver developers only.
  74. If in doubt, say "N".
  75. config DRM_I915_DEBUG_GUC
  76. bool "Enable additional driver debugging for GuC"
  77. depends on DRM_I915
  78. default n
  79. help
  80. Choose this option to turn on extra driver debugging that may affect
  81. performance but will help resolve GuC related issues.
  82. Recommended for driver developers only.
  83. If in doubt, say "N".
  84. config DRM_I915_SELFTEST
  85. bool "Enable selftests upon driver load"
  86. depends on DRM_I915
  87. default n
  88. select FAULT_INJECTION
  89. select PRIME_NUMBERS
  90. help
  91. Choose this option to allow the driver to perform selftests upon
  92. loading; also requires the i915.selftest=1 module parameter. To
  93. exit the module after running the selftests (i.e. to prevent normal
  94. module initialisation afterwards) use i915.selftest=-1.
  95. Recommended for driver developers only.
  96. If in doubt, say "N".
  97. config DRM_I915_SELFTEST_BROKEN
  98. bool "Enable broken and dangerous selftests"
  99. depends on DRM_I915_SELFTEST
  100. depends on BROKEN
  101. default n
  102. help
  103. This option enables the execution of selftests that are "dangerous"
  104. and may trigger unintended HW side-effects as they break strict
  105. rules given in the HW specification. For science.
  106. Recommended for masochistic driver developers only.
  107. If in doubt, say "N".
  108. config DRM_I915_LOW_LEVEL_TRACEPOINTS
  109. bool "Enable low level request tracing events"
  110. depends on DRM_I915
  111. default n
  112. help
  113. Choose this option to turn on low level request tracing events.
  114. This provides the ability to precisely monitor engine utilisation
  115. and also analyze the request dependency resolving timeline.
  116. If in doubt, say "N".
  117. config DRM_I915_DEBUG_VBLANK_EVADE
  118. bool "Enable extra debug warnings for vblank evasion"
  119. depends on DRM_I915
  120. default n
  121. help
  122. Choose this option to turn on extra debug warnings for the
  123. vblank evade mechanism. This gives a warning every time the
  124. the deadline allotted for the vblank evade critical section
  125. is exceeded, even if there isn't an actual risk of missing
  126. the vblank.
  127. If in doubt, say "N".