brintos

brintos / linux-shallow public Read only

0
0
Text · 9.2 KiB · b288d99 Raw
303 lines · plain
1# SPDX-License-Identifier: GPL-2.0-only2menuconfig SAMPLES3	bool "Sample kernel code"4	help5	  You can build and test sample kernel code here.6 7if SAMPLES8 9config SAMPLE_AUXDISPLAY10	bool "auxdisplay sample"11	depends on CC_CAN_LINK12 13config SAMPLE_TRACE_EVENTS14	tristate "Build trace_events examples -- loadable modules only"15	depends on EVENT_TRACING && m16	help17	  This builds the trace event example module.18 19config SAMPLE_TRACE_CUSTOM_EVENTS20	tristate "Build custom trace event example -- loadable modules only"21	depends on EVENT_TRACING && m22	help23	  This builds the custom trace event example module.24 25config SAMPLE_TRACE_PRINTK26        tristate "Build trace_printk module - tests various trace_printk formats"27	depends on EVENT_TRACING && m28	help29	 This builds a module that calls trace_printk() and can be used to30	 test various trace_printk() calls from a module.31 32config SAMPLE_FTRACE_DIRECT33	tristate "Build register_ftrace_direct() example"34	depends on DYNAMIC_FTRACE_WITH_DIRECT_CALLS && m35	depends on HAVE_SAMPLE_FTRACE_DIRECT36	help37	  This builds an ftrace direct function example38	  that hooks to wake_up_process and prints the parameters.39 40config SAMPLE_FTRACE_DIRECT_MULTI41	tristate "Build register_ftrace_direct() on multiple ips example"42	depends on DYNAMIC_FTRACE_WITH_DIRECT_CALLS && m43	depends on HAVE_SAMPLE_FTRACE_DIRECT_MULTI44	help45	  This builds an ftrace direct function example46	  that hooks to wake_up_process and schedule, and prints47	  the function addresses.48 49config SAMPLE_FTRACE_OPS50	tristate "Build custom ftrace ops example"51	depends on FUNCTION_TRACER52	help53	  This builds an ftrace ops example that hooks two functions and54	  measures the time taken to invoke one function a number of times.55 56config SAMPLE_TRACE_ARRAY57        tristate "Build sample module for kernel access to Ftrace instancess"58	depends on EVENT_TRACING && m59	help60	 This builds a module that demonstrates the use of various APIs to61	 access Ftrace instances from within the kernel.62 63config SAMPLE_KOBJECT64	tristate "Build kobject examples"65	help66	  This config option will allow you to build a number of67	  different kobject sample modules showing how to use kobjects,68	  ksets, and ktypes properly.69 70	  If in doubt, say "N" here.71 72config SAMPLE_KPROBES73	tristate "Build kprobes examples -- loadable modules only"74	depends on KPROBES && m75	help76	  This build several kprobes example modules.77 78config SAMPLE_KRETPROBES79	tristate "Build kretprobes example -- loadable modules only"80	default m81	depends on SAMPLE_KPROBES && KRETPROBES82 83config SAMPLE_HW_BREAKPOINT84	tristate "Build kernel hardware breakpoint examples -- loadable module only"85	depends on HAVE_HW_BREAKPOINT && m86	help87	  This builds kernel hardware breakpoint example modules.88 89config SAMPLE_FPROBE90	tristate "Build fprobe examples -- loadable modules only"91	depends on FPROBE && m92	help93	  This builds a fprobe example module. This module has an option 'symbol'.94	  You can specify a probed symbol or symbols separated with ','.95 96config SAMPLE_KFIFO97	tristate "Build kfifo examples -- loadable modules only"98	depends on m99	help100	  This config option will allow you to build a number of101	  different kfifo sample modules showing how to use the102	  generic kfifo API.103 104	  If in doubt, say "N" here.105 106config SAMPLE_KDB107	tristate "Build kdb command example -- loadable modules only"108	depends on KGDB_KDB && m109	help110	  Build an example of how to dynamically add the hello111	  command to the kdb shell.112 113config SAMPLE_QMI_CLIENT114	tristate "Build qmi client sample -- loadable modules only"115	depends on m116	depends on ARCH_QCOM117	depends on NET118	select QCOM_QMI_HELPERS119	help120	  Build an QMI client sample driver, which demonstrates how to121	  communicate with a remote QRTR service, using QMI encoded messages.122 123config SAMPLE_RPMSG_CLIENT124	tristate "Build rpmsg client sample -- loadable modules only"125	depends on RPMSG && m126	help127	  Build an rpmsg client sample driver, which demonstrates how128	  to communicate with an AMP-configured remote processor over129	  the rpmsg bus.130 131config SAMPLE_LIVEPATCH132	tristate "Build live patching samples -- loadable modules only"133	depends on LIVEPATCH && m134	help135	  Build sample live patch demonstrations.136 137config SAMPLE_CONFIGFS138	tristate "Build configfs patching sample -- loadable modules only"139	depends on CONFIGFS_FS && m140	help141	  Builds a sample configfs interface.142 143config SAMPLE_CONNECTOR144	tristate "Build connector sample -- loadable modules only"145	depends on CONNECTOR && HEADERS_INSTALL && m146	help147	  When enabled, this builds both a sample kernel module for148	  the connector interface and a user space tool to communicate149	  with it.150	  See also Documentation/driver-api/connector.rst151 152config SAMPLE_FANOTIFY_ERROR153	bool "Build fanotify error monitoring sample"154	depends on FANOTIFY && CC_CAN_LINK && HEADERS_INSTALL155	help156	  When enabled, this builds an example code that uses the157	  FAN_FS_ERROR fanotify mechanism to monitor filesystem158	  errors.159	  See also Documentation/admin-guide/filesystem-monitoring.rst.160 161config SAMPLE_HIDRAW162	bool "hidraw sample"163	depends on CC_CAN_LINK && HEADERS_INSTALL164 165config SAMPLE_LANDLOCK166	bool "Landlock example"167	depends on CC_CAN_LINK && HEADERS_INSTALL168	help169	  Build a simple Landlock sandbox manager able to start a process170	  restricted by a user-defined filesystem access control policy.171 172config SAMPLE_PIDFD173	bool "pidfd sample"174	depends on CC_CAN_LINK && HEADERS_INSTALL175 176config SAMPLE_SECCOMP177	bool "Build seccomp sample code"178	depends on SECCOMP_FILTER && CC_CAN_LINK && HEADERS_INSTALL179	help180	  Build samples of seccomp filters using various methods of181	  BPF filter construction.182 183config SAMPLE_TIMER184	bool "Timer sample"185	depends on CC_CAN_LINK && HEADERS_INSTALL186 187config SAMPLE_UHID188	bool "UHID sample"189	depends on CC_CAN_LINK && HEADERS_INSTALL190	help191	  Build UHID sample program.192 193config SAMPLE_VFIO_MDEV_MTTY194	tristate "Build VFIO mtty example mediated device sample code"195	depends on VFIO196	select VFIO_MDEV197	help198	  Build a virtual tty sample driver for use as a VFIO199	  mediated device200 201config SAMPLE_VFIO_MDEV_MDPY202	tristate "Build VFIO mdpy example mediated device sample code"203	depends on VFIO204	select VFIO_MDEV205	help206	  Build a virtual display sample driver for use as a VFIO207	  mediated device.  It is a simple framebuffer and supports208	  the region display interface (VFIO_GFX_PLANE_TYPE_REGION).209 210config SAMPLE_VFIO_MDEV_MDPY_FB211	tristate "Build VFIO mdpy example guest fbdev driver"212	depends on FB213	select FB_IOMEM_HELPERS214	help215	  Guest fbdev driver for the virtual display sample driver.216 217config SAMPLE_VFIO_MDEV_MBOCHS218	tristate "Build VFIO mbochs example mediated device sample code"219	depends on VFIO220	select VFIO_MDEV221	select DMA_SHARED_BUFFER222	help223	  Build a virtual display sample driver for use as a VFIO224	  mediated device.  It supports the region display interface225	  (VFIO_GFX_PLANE_TYPE_DMABUF).226	  Emulate enough of qemu stdvga to make bochs-drm.ko happy.227	  That is basically the vram memory bar and the bochs dispi228	  interface vbe registers in the mmio register bar.229	  Specifically it does *not* include any legacy vga stuff.230	  Device looks a lot like "qemu -device secondary-vga".231 232config SAMPLE_ANDROID_BINDERFS233	bool "Build Android binderfs example"234	depends on CC_CAN_LINK && HEADERS_INSTALL235	help236	  Builds a sample program to illustrate the use of the Android binderfs237	  filesystem.238 239config SAMPLE_VFS240	bool "Build example programs that use new VFS system calls"241	depends on CC_CAN_LINK && HEADERS_INSTALL242	help243	  Build example userspace programs that use new VFS system calls such244	  as mount API and statx().  Note that this is restricted to the x86245	  arch whilst it accesses system calls that aren't yet in all arches.246 247config SAMPLE_INTEL_MEI248	bool "Build example program working with intel mei driver"249	depends on INTEL_MEI250	depends on CC_CAN_LINK && HEADERS_INSTALL251	help252	  Build a sample program to work with mei device.253 254config SAMPLE_TPS6594_PFSM255	bool "Build example program working with TPS6594 PFSM driver"256	depends on HEADERS_INSTALL257	depends on CC_CAN_LINK258	help259	  Build a sample program to work with PFSM devices.260 261config SAMPLE_WATCHDOG262	bool "watchdog sample"263	depends on CC_CAN_LINK264 265config SAMPLE_WATCH_QUEUE266	bool "Build example watch_queue notification API consumer"267	depends on CC_CAN_LINK && HEADERS_INSTALL268	help269	  Build example userspace program to use the new mount_notify(),270	  sb_notify() syscalls and the KEYCTL_WATCH_KEY keyctl() function.271 272config SAMPLE_CORESIGHT_SYSCFG273	tristate "Build example loadable module for CoreSight config"274	depends on CORESIGHT && m275	help276	  Build an example loadable module that adds new CoreSight features277	  and configuration using the CoreSight system configuration API.278	  This demonstrates how a user may create their own CoreSight279	  configurations and easily load them into the system at runtime.280 281config SAMPLE_KMEMLEAK282        tristate "Simple test for the kernel memory leak detector"283        depends on DEBUG_KMEMLEAK && m284        help285          Build a sample program which have explicitly leaks memory to test286          kmemleak287 288config SAMPLE_CGROUP289	bool "Build cgroup sample code"290	depends on CGROUPS && CC_CAN_LINK && HEADERS_INSTALL291	help292	  Build samples that demonstrate the usage of the cgroup API.293 294source "samples/rust/Kconfig"295 296endif # SAMPLES297 298config HAVE_SAMPLE_FTRACE_DIRECT299	bool300 301config HAVE_SAMPLE_FTRACE_DIRECT_MULTI302	bool303