Kconfig 4.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157
  1. menuconfig SAMPLES
  2. bool "Sample kernel code"
  3. depends on !UML
  4. help
  5. You can build and test sample kernel code here.
  6. if SAMPLES
  7. config SAMPLE_TRACE_EVENTS
  8. tristate "Build trace_events examples -- loadable modules only"
  9. depends on EVENT_TRACING && m
  10. help
  11. This build trace event example modules.
  12. config SAMPLE_TRACE_PRINTK
  13. tristate "Build trace_printk module - tests various trace_printk formats"
  14. depends on EVENT_TRACING && m
  15. help
  16. This builds a module that calls trace_printk() and can be used to
  17. test various trace_printk() calls from a module.
  18. config SAMPLE_KOBJECT
  19. tristate "Build kobject examples -- loadable modules only"
  20. depends on m
  21. help
  22. This config option will allow you to build a number of
  23. different kobject sample modules showing how to use kobjects,
  24. ksets, and ktypes properly.
  25. If in doubt, say "N" here.
  26. config SAMPLE_KPROBES
  27. tristate "Build kprobes examples -- loadable modules only"
  28. depends on KPROBES && m
  29. help
  30. This build several kprobes example modules.
  31. config SAMPLE_KRETPROBES
  32. tristate "Build kretprobes example -- loadable modules only"
  33. default m
  34. depends on SAMPLE_KPROBES && KRETPROBES
  35. config SAMPLE_HW_BREAKPOINT
  36. tristate "Build kernel hardware breakpoint examples -- loadable module only"
  37. depends on HAVE_HW_BREAKPOINT && m
  38. help
  39. This builds kernel hardware breakpoint example modules.
  40. config SAMPLE_KFIFO
  41. tristate "Build kfifo examples -- loadable modules only"
  42. depends on m
  43. help
  44. This config option will allow you to build a number of
  45. different kfifo sample modules showing how to use the
  46. generic kfifo API.
  47. If in doubt, say "N" here.
  48. config SAMPLE_KDB
  49. tristate "Build kdb command example -- loadable modules only"
  50. depends on KGDB_KDB && m
  51. help
  52. Build an example of how to dynamically add the hello
  53. command to the kdb shell.
  54. config SAMPLE_QMI_CLIENT
  55. tristate "Build qmi client sample -- loadable modules only"
  56. depends on m
  57. depends on ARCH_QCOM
  58. depends on NET
  59. select QCOM_QMI_HELPERS
  60. help
  61. Build an QMI client sample driver, which demonstrates how to
  62. communicate with a remote QRTR service, using QMI encoded messages.
  63. config SAMPLE_RPMSG_CLIENT
  64. tristate "Build rpmsg client sample -- loadable modules only"
  65. depends on RPMSG && m
  66. help
  67. Build an rpmsg client sample driver, which demonstrates how
  68. to communicate with an AMP-configured remote processor over
  69. the rpmsg bus.
  70. config SAMPLE_LIVEPATCH
  71. tristate "Build live patching samples -- loadable modules only"
  72. depends on LIVEPATCH && m
  73. help
  74. Build sample live patch demonstrations.
  75. config SAMPLE_CONFIGFS
  76. tristate "Build configfs patching sample -- loadable modules only"
  77. depends on CONFIGFS_FS && m
  78. help
  79. Builds a sample configfs interface.
  80. config SAMPLE_CONNECTOR
  81. tristate "Build connector sample -- loadable modules only"
  82. depends on CONNECTOR && m
  83. help
  84. When enabled, this builds both a sample kernel module for
  85. the connector interface and a user space tool to communicate
  86. with it.
  87. See also Documentation/connector/connector.txt
  88. config SAMPLE_SECCOMP
  89. tristate "Build seccomp sample code -- loadable modules only"
  90. depends on SECCOMP_FILTER && m
  91. help
  92. Build samples of seccomp filters using various methods of
  93. BPF filter construction.
  94. config SAMPLE_VFIO_MDEV_MTTY
  95. tristate "Build VFIO mtty example mediated device sample code -- loadable modules only"
  96. depends on VFIO_MDEV_DEVICE && m
  97. help
  98. Build a virtual tty sample driver for use as a VFIO
  99. mediated device
  100. config SAMPLE_VFIO_MDEV_MDPY
  101. tristate "Build VFIO mdpy example mediated device sample code -- loadable modules only"
  102. depends on VFIO_MDEV_DEVICE && m
  103. help
  104. Build a virtual display sample driver for use as a VFIO
  105. mediated device. It is a simple framebuffer and supports
  106. the region display interface (VFIO_GFX_PLANE_TYPE_REGION).
  107. config SAMPLE_VFIO_MDEV_MDPY_FB
  108. tristate "Build VFIO mdpy example guest fbdev driver -- loadable module only"
  109. depends on FB && m
  110. select FB_CFB_FILLRECT
  111. select FB_CFB_COPYAREA
  112. select FB_CFB_IMAGEBLIT
  113. help
  114. Guest fbdev driver for the virtual display sample driver.
  115. config SAMPLE_VFIO_MDEV_MBOCHS
  116. tristate "Build VFIO mdpy example mediated device sample code -- loadable modules only"
  117. depends on VFIO_MDEV_DEVICE && m
  118. select DMA_SHARED_BUFFER
  119. help
  120. Build a virtual display sample driver for use as a VFIO
  121. mediated device. It supports the region display interface
  122. (VFIO_GFX_PLANE_TYPE_DMABUF).
  123. Emulate enough of qemu stdvga to make bochs-drm.ko happy.
  124. That is basically the vram memory bar and the bochs dispi
  125. interface vbe registers in the mmio register bar.
  126. Specifically it does *not* include any legacy vga stuff.
  127. Device looks a lot like "qemu -device secondary-vga".
  128. config SAMPLE_STATX
  129. bool "Build example extended-stat using code"
  130. depends on BROKEN
  131. help
  132. Build example userspace program to use the new extended-stat syscall.
  133. endif # SAMPLES