Kconfig 20 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734
  1. #
  2. # For a description of the syntax of this configuration file,
  3. # see Documentation/kbuild/kconfig-language.txt.
  4. #
  5. # Note: ISA is disabled and will hopefully never be enabled.
  6. # If you managed to buy an ISA x86-64 box you'll have to fix all the
  7. # ISA drivers you need yourself.
  8. #
  9. mainmenu "Linux Kernel Configuration"
  10. config X86_64
  11. bool
  12. default y
  13. help
  14. Port to the x86-64 architecture. x86-64 is a 64-bit extension to the
  15. classical 32-bit x86 architecture. For details see
  16. <http://www.x86-64.org/>.
  17. config 64BIT
  18. def_bool y
  19. config X86
  20. bool
  21. default y
  22. config ZONE_DMA32
  23. bool
  24. default y
  25. config LOCKDEP_SUPPORT
  26. bool
  27. default y
  28. config STACKTRACE_SUPPORT
  29. bool
  30. default y
  31. config SEMAPHORE_SLEEPERS
  32. bool
  33. default y
  34. config MMU
  35. bool
  36. default y
  37. config ISA
  38. bool
  39. config SBUS
  40. bool
  41. config RWSEM_GENERIC_SPINLOCK
  42. bool
  43. default y
  44. config RWSEM_XCHGADD_ALGORITHM
  45. bool
  46. config GENERIC_HWEIGHT
  47. bool
  48. default y
  49. config GENERIC_CALIBRATE_DELAY
  50. bool
  51. default y
  52. config X86_CMPXCHG
  53. bool
  54. default y
  55. config EARLY_PRINTK
  56. bool
  57. default y
  58. config GENERIC_ISA_DMA
  59. bool
  60. default y
  61. config GENERIC_IOMAP
  62. bool
  63. default y
  64. config ARCH_MAY_HAVE_PC_FDC
  65. bool
  66. default y
  67. config ARCH_POPULATES_NODE_MAP
  68. def_bool y
  69. config DMI
  70. bool
  71. default y
  72. config AUDIT_ARCH
  73. bool
  74. default y
  75. config GENERIC_BUG
  76. bool
  77. default y
  78. depends on BUG
  79. source "init/Kconfig"
  80. menu "Processor type and features"
  81. choice
  82. prompt "Subarchitecture Type"
  83. default X86_PC
  84. config X86_PC
  85. bool "PC-compatible"
  86. help
  87. Choose this option if your computer is a standard PC or compatible.
  88. config X86_VSMP
  89. bool "Support for ScaleMP vSMP"
  90. depends on PCI
  91. help
  92. Support for ScaleMP vSMP systems. Say 'Y' here if this kernel is
  93. supposed to run on these EM64T-based machines. Only choose this option
  94. if you have one of these machines.
  95. endchoice
  96. choice
  97. prompt "Processor family"
  98. default GENERIC_CPU
  99. config MK8
  100. bool "AMD-Opteron/Athlon64"
  101. help
  102. Optimize for AMD Opteron/Athlon64/Hammer/K8 CPUs.
  103. config MPSC
  104. bool "Intel P4 / older Netburst based Xeon"
  105. help
  106. Optimize for Intel Pentium 4 and older Nocona/Dempsey Xeon CPUs
  107. with Intel Extended Memory 64 Technology(EM64T). For details see
  108. <http://www.intel.com/technology/64bitextensions/>.
  109. Note the the latest Xeons (Xeon 51xx and 53xx) are not based on the
  110. Netburst core and shouldn't use this option. You can distingush them
  111. using the cpu family field
  112. in /proc/cpuinfo. Family 15 is a older Xeon, Family 6 a newer one
  113. (this rule only applies to system that support EM64T)
  114. config MCORE2
  115. bool "Intel Core2 / newer Xeon"
  116. help
  117. Optimize for Intel Core2 and newer Xeons (51xx)
  118. You can distingush the newer Xeons from the older ones using
  119. the cpu family field in /proc/cpuinfo. 15 is a older Xeon
  120. (use CONFIG_MPSC then), 6 is a newer one. This rule only
  121. applies to CPUs that support EM64T.
  122. config GENERIC_CPU
  123. bool "Generic-x86-64"
  124. help
  125. Generic x86-64 CPU.
  126. Run equally well on all x86-64 CPUs.
  127. endchoice
  128. #
  129. # Define implied options from the CPU selection here
  130. #
  131. config X86_L1_CACHE_BYTES
  132. int
  133. default "128" if GENERIC_CPU || MPSC
  134. default "64" if MK8 || MCORE2
  135. config X86_L1_CACHE_SHIFT
  136. int
  137. default "7" if GENERIC_CPU || MPSC
  138. default "6" if MK8 || MCORE2
  139. config X86_INTERNODE_CACHE_BYTES
  140. int
  141. default "4096" if X86_VSMP
  142. default X86_L1_CACHE_BYTES if !X86_VSMP
  143. config X86_TSC
  144. bool
  145. default y
  146. config X86_GOOD_APIC
  147. bool
  148. default y
  149. config MICROCODE
  150. tristate "/dev/cpu/microcode - Intel CPU microcode support"
  151. select FW_LOADER
  152. ---help---
  153. If you say Y here the 'File systems' section, you will be
  154. able to update the microcode on Intel processors. You will
  155. obviously need the actual microcode binary data itself which is
  156. not shipped with the Linux kernel.
  157. For latest news and information on obtaining all the required
  158. ingredients for this driver, check:
  159. <http://www.urbanmyth.org/microcode/>.
  160. To compile this driver as a module, choose M here: the
  161. module will be called microcode.
  162. If you use modprobe or kmod you may also want to add the line
  163. 'alias char-major-10-184 microcode' to your /etc/modules.conf file.
  164. config MICROCODE_OLD_INTERFACE
  165. bool
  166. depends on MICROCODE
  167. default y
  168. config X86_MSR
  169. tristate "/dev/cpu/*/msr - Model-specific register support"
  170. help
  171. This device gives privileged processes access to the x86
  172. Model-Specific Registers (MSRs). It is a character device with
  173. major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
  174. MSR accesses are directed to a specific CPU on multi-processor
  175. systems.
  176. config X86_CPUID
  177. tristate "/dev/cpu/*/cpuid - CPU information support"
  178. help
  179. This device gives processes access to the x86 CPUID instruction to
  180. be executed on a specific processor. It is a character device
  181. with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
  182. /dev/cpu/31/cpuid.
  183. config X86_HT
  184. bool
  185. depends on SMP && !MK8
  186. default y
  187. config MATH_EMULATION
  188. bool
  189. config MCA
  190. bool
  191. config EISA
  192. bool
  193. config X86_IO_APIC
  194. bool
  195. default y
  196. config X86_LOCAL_APIC
  197. bool
  198. default y
  199. config MTRR
  200. bool "MTRR (Memory Type Range Register) support"
  201. ---help---
  202. On Intel P6 family processors (Pentium Pro, Pentium II and later)
  203. the Memory Type Range Registers (MTRRs) may be used to control
  204. processor access to memory ranges. This is most useful if you have
  205. a video (VGA) card on a PCI or AGP bus. Enabling write-combining
  206. allows bus write transfers to be combined into a larger transfer
  207. before bursting over the PCI/AGP bus. This can increase performance
  208. of image write operations 2.5 times or more. Saying Y here creates a
  209. /proc/mtrr file which may be used to manipulate your processor's
  210. MTRRs. Typically the X server should use this.
  211. This code has a reasonably generic interface so that similar
  212. control registers on other processors can be easily supported
  213. as well.
  214. Saying Y here also fixes a problem with buggy SMP BIOSes which only
  215. set the MTRRs for the boot CPU and not for the secondary CPUs. This
  216. can lead to all sorts of problems, so it's good to say Y here.
  217. Just say Y here, all x86-64 machines support MTRRs.
  218. See <file:Documentation/mtrr.txt> for more information.
  219. config SMP
  220. bool "Symmetric multi-processing support"
  221. ---help---
  222. This enables support for systems with more than one CPU. If you have
  223. a system with only one CPU, like most personal computers, say N. If
  224. you have a system with more than one CPU, say Y.
  225. If you say N here, the kernel will run on single and multiprocessor
  226. machines, but will use only one CPU of a multiprocessor machine. If
  227. you say Y here, the kernel will run on many, but not all,
  228. singleprocessor machines. On a singleprocessor machine, the kernel
  229. will run faster if you say N here.
  230. If you don't know what to do here, say N.
  231. config SCHED_SMT
  232. bool "SMT (Hyperthreading) scheduler support"
  233. depends on SMP
  234. default n
  235. help
  236. SMT scheduler support improves the CPU scheduler's decision making
  237. when dealing with Intel Pentium 4 chips with HyperThreading at a
  238. cost of slightly increased overhead in some places. If unsure say
  239. N here.
  240. config SCHED_MC
  241. bool "Multi-core scheduler support"
  242. depends on SMP
  243. default y
  244. help
  245. Multi-core scheduler support improves the CPU scheduler's decision
  246. making when dealing with multi-core CPU chips at a cost of slightly
  247. increased overhead in some places. If unsure say N here.
  248. source "kernel/Kconfig.preempt"
  249. config NUMA
  250. bool "Non Uniform Memory Access (NUMA) Support"
  251. depends on SMP
  252. help
  253. Enable NUMA (Non Uniform Memory Access) support. The kernel
  254. will try to allocate memory used by a CPU on the local memory
  255. controller of the CPU and add some more NUMA awareness to the kernel.
  256. This code is recommended on all multiprocessor Opteron systems.
  257. If the system is EM64T, you should say N unless your system is EM64T
  258. NUMA.
  259. config K8_NUMA
  260. bool "Old style AMD Opteron NUMA detection"
  261. depends on NUMA && PCI
  262. default y
  263. help
  264. Enable K8 NUMA node topology detection. You should say Y here if
  265. you have a multi processor AMD K8 system. This uses an old
  266. method to read the NUMA configuration directly from the builtin
  267. Northbridge of Opteron. It is recommended to use X86_64_ACPI_NUMA
  268. instead, which also takes priority if both are compiled in.
  269. config NODES_SHIFT
  270. int
  271. default "6"
  272. depends on NEED_MULTIPLE_NODES
  273. # Dummy CONFIG option to select ACPI_NUMA from drivers/acpi/Kconfig.
  274. config X86_64_ACPI_NUMA
  275. bool "ACPI NUMA detection"
  276. depends on NUMA
  277. select ACPI
  278. select PCI
  279. select ACPI_NUMA
  280. default y
  281. help
  282. Enable ACPI SRAT based node topology detection.
  283. config NUMA_EMU
  284. bool "NUMA emulation"
  285. depends on NUMA
  286. help
  287. Enable NUMA emulation. A flat machine will be split
  288. into virtual nodes when booted with "numa=fake=N", where N is the
  289. number of nodes. This is only useful for debugging.
  290. config ARCH_DISCONTIGMEM_ENABLE
  291. bool
  292. depends on NUMA
  293. default y
  294. config ARCH_DISCONTIGMEM_DEFAULT
  295. def_bool y
  296. depends on NUMA
  297. config ARCH_SPARSEMEM_ENABLE
  298. def_bool y
  299. depends on (NUMA || EXPERIMENTAL)
  300. config ARCH_MEMORY_PROBE
  301. def_bool y
  302. depends on MEMORY_HOTPLUG
  303. config ARCH_FLATMEM_ENABLE
  304. def_bool y
  305. depends on !NUMA
  306. source "mm/Kconfig"
  307. config MEMORY_HOTPLUG_RESERVE
  308. def_bool y
  309. depends on (MEMORY_HOTPLUG && DISCONTIGMEM)
  310. config HAVE_ARCH_EARLY_PFN_TO_NID
  311. def_bool y
  312. depends on NUMA
  313. config OUT_OF_LINE_PFN_TO_PAGE
  314. def_bool y
  315. depends on DISCONTIGMEM
  316. config NR_CPUS
  317. int "Maximum number of CPUs (2-256)"
  318. range 2 255
  319. depends on SMP
  320. default "8"
  321. help
  322. This allows you to specify the maximum number of CPUs which this
  323. kernel will support. Current maximum is 256 CPUs due to
  324. APIC addressing limits. Less depending on the hardware.
  325. This is purely to save memory - each supported CPU requires
  326. memory in the static kernel configuration.
  327. config HOTPLUG_CPU
  328. bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
  329. depends on SMP && HOTPLUG && EXPERIMENTAL
  330. help
  331. Say Y here to experiment with turning CPUs off and on. CPUs
  332. can be controlled through /sys/devices/system/cpu/cpu#.
  333. Say N if you want to disable CPU hotplug.
  334. config ARCH_ENABLE_MEMORY_HOTPLUG
  335. def_bool y
  336. config HPET_TIMER
  337. bool
  338. default y
  339. help
  340. Use the IA-PC HPET (High Precision Event Timer) to manage
  341. time in preference to the PIT and RTC, if a HPET is
  342. present. The HPET provides a stable time base on SMP
  343. systems, unlike the TSC, but it is more expensive to access,
  344. as it is off-chip. You can find the HPET spec at
  345. <http://www.intel.com/hardwaredesign/hpetspec.htm>.
  346. config HPET_EMULATE_RTC
  347. bool "Provide RTC interrupt"
  348. depends on HPET_TIMER && RTC=y
  349. # Mark as embedded because too many people got it wrong.
  350. # The code disables itself when not needed.
  351. config IOMMU
  352. bool "IOMMU support" if EMBEDDED
  353. default y
  354. select SWIOTLB
  355. select AGP
  356. depends on PCI
  357. help
  358. Support for full DMA access of devices with 32bit memory access only
  359. on systems with more than 3GB. This is usually needed for USB,
  360. sound, many IDE/SATA chipsets and some other devices.
  361. Provides a driver for the AMD Athlon64/Opteron/Turion/Sempron GART
  362. based IOMMU and a software bounce buffer based IOMMU used on Intel
  363. systems and as fallback.
  364. The code is only active when needed (enough memory and limited
  365. device) unless CONFIG_IOMMU_DEBUG or iommu=force is specified
  366. too.
  367. config CALGARY_IOMMU
  368. bool "IBM Calgary IOMMU support"
  369. select SWIOTLB
  370. depends on PCI && EXPERIMENTAL
  371. help
  372. Support for hardware IOMMUs in IBM's xSeries x366 and x460
  373. systems. Needed to run systems with more than 3GB of memory
  374. properly with 32-bit PCI devices that do not support DAC
  375. (Double Address Cycle). Calgary also supports bus level
  376. isolation, where all DMAs pass through the IOMMU. This
  377. prevents them from going anywhere except their intended
  378. destination. This catches hard-to-find kernel bugs and
  379. mis-behaving drivers and devices that do not use the DMA-API
  380. properly to set up their DMA buffers. The IOMMU can be
  381. turned off at boot time with the iommu=off parameter.
  382. Normally the kernel will make the right choice by itself.
  383. If unsure, say Y.
  384. config CALGARY_IOMMU_ENABLED_BY_DEFAULT
  385. bool "Should Calgary be enabled by default?"
  386. default y
  387. depends on CALGARY_IOMMU
  388. help
  389. Should Calgary be enabled by default? if you choose 'y', Calgary
  390. will be used (if it exists). If you choose 'n', Calgary will not be
  391. used even if it exists. If you choose 'n' and would like to use
  392. Calgary anyway, pass 'iommu=calgary' on the kernel command line.
  393. If unsure, say Y.
  394. # need this always selected by IOMMU for the VIA workaround
  395. config SWIOTLB
  396. bool
  397. config X86_MCE
  398. bool "Machine check support" if EMBEDDED
  399. default y
  400. help
  401. Include a machine check error handler to report hardware errors.
  402. This version will require the mcelog utility to decode some
  403. machine check error logs. See
  404. ftp://ftp.x86-64.org/pub/linux/tools/mcelog
  405. config X86_MCE_INTEL
  406. bool "Intel MCE features"
  407. depends on X86_MCE && X86_LOCAL_APIC
  408. default y
  409. help
  410. Additional support for intel specific MCE features such as
  411. the thermal monitor.
  412. config X86_MCE_AMD
  413. bool "AMD MCE features"
  414. depends on X86_MCE && X86_LOCAL_APIC
  415. default y
  416. help
  417. Additional support for AMD specific MCE features such as
  418. the DRAM Error Threshold.
  419. config KEXEC
  420. bool "kexec system call"
  421. help
  422. kexec is a system call that implements the ability to shutdown your
  423. current kernel, and to start another kernel. It is like a reboot
  424. but it is independent of the system firmware. And like a reboot
  425. you can start any kernel with it, not just Linux.
  426. The name comes from the similarity to the exec system call.
  427. It is an ongoing process to be certain the hardware in a machine
  428. is properly shutdown, so do not be surprised if this code does not
  429. initially work for you. It may help to enable device hotplugging
  430. support. As of this writing the exact hardware interface is
  431. strongly in flux, so no good recommendation can be made.
  432. config CRASH_DUMP
  433. bool "kernel crash dumps (EXPERIMENTAL)"
  434. depends on EXPERIMENTAL
  435. help
  436. Generate crash dump after being started by kexec.
  437. This should be normally only set in special crash dump kernels
  438. which are loaded in the main kernel with kexec-tools into
  439. a specially reserved region and then later executed after
  440. a crash by kdump/kexec. The crash dump kernel must be compiled
  441. to a memory address not used by the main kernel or BIOS using
  442. PHYSICAL_START.
  443. For more details see Documentation/kdump/kdump.txt
  444. config PHYSICAL_START
  445. hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
  446. default "0x1000000" if CRASH_DUMP
  447. default "0x200000"
  448. help
  449. This gives the physical address where the kernel is loaded. Normally
  450. for regular kernels this value is 0x200000 (2MB). But in the case
  451. of kexec on panic the fail safe kernel needs to run at a different
  452. address than the panic-ed kernel. This option is used to set the load
  453. address for kernels used to capture crash dump on being kexec'ed
  454. after panic. The default value for crash dump kernels is
  455. 0x1000000 (16MB). This can also be set based on the "X" value as
  456. specified in the "crashkernel=YM@XM" command line boot parameter
  457. passed to the panic-ed kernel. Typically this parameter is set as
  458. crashkernel=64M@16M. Please take a look at
  459. Documentation/kdump/kdump.txt for more details about crash dumps.
  460. Don't change this unless you know what you are doing.
  461. config SECCOMP
  462. bool "Enable seccomp to safely compute untrusted bytecode"
  463. depends on PROC_FS
  464. default y
  465. help
  466. This kernel feature is useful for number crunching applications
  467. that may need to compute untrusted bytecode during their
  468. execution. By using pipes or other transports made available to
  469. the process as file descriptors supporting the read/write
  470. syscalls, it's possible to isolate those applications in
  471. their own address space using seccomp. Once seccomp is
  472. enabled via /proc/<pid>/seccomp, it cannot be disabled
  473. and the task is only allowed to execute a few safe syscalls
  474. defined by each seccomp mode.
  475. If unsure, say Y. Only embedded should say N here.
  476. config CC_STACKPROTECTOR
  477. bool "Enable -fstack-protector buffer overflow detection (EXPRIMENTAL)"
  478. depends on EXPERIMENTAL
  479. help
  480. This option turns on the -fstack-protector GCC feature. This
  481. feature puts, at the beginning of critical functions, a canary
  482. value on the stack just before the return address, and validates
  483. the value just before actually returning. Stack based buffer
  484. overflows (that need to overwrite this return address) now also
  485. overwrite the canary, which gets detected and the attack is then
  486. neutralized via a kernel panic.
  487. This feature requires gcc version 4.2 or above, or a distribution
  488. gcc with the feature backported. Older versions are automatically
  489. detected and for those versions, this configuration option is ignored.
  490. config CC_STACKPROTECTOR_ALL
  491. bool "Use stack-protector for all functions"
  492. depends on CC_STACKPROTECTOR
  493. help
  494. Normally, GCC only inserts the canary value protection for
  495. functions that use large-ish on-stack buffers. By enabling
  496. this option, GCC will be asked to do this for ALL functions.
  497. source kernel/Kconfig.hz
  498. config REORDER
  499. bool "Function reordering"
  500. default n
  501. help
  502. This option enables the toolchain to reorder functions for a more
  503. optimal TLB usage. If you have pretty much any version of binutils,
  504. this can increase your kernel build time by roughly one minute.
  505. config K8_NB
  506. def_bool y
  507. depends on AGP_AMD64 || IOMMU || (PCI && NUMA)
  508. endmenu
  509. #
  510. # Use the generic interrupt handling code in kernel/irq/:
  511. #
  512. config GENERIC_HARDIRQS
  513. bool
  514. default y
  515. config GENERIC_IRQ_PROBE
  516. bool
  517. default y
  518. # we have no ISA slots, but we do have ISA-style DMA.
  519. config ISA_DMA_API
  520. bool
  521. default y
  522. config GENERIC_PENDING_IRQ
  523. bool
  524. depends on GENERIC_HARDIRQS && SMP
  525. default y
  526. menu "Power management options"
  527. source kernel/power/Kconfig
  528. source "drivers/acpi/Kconfig"
  529. source "arch/x86_64/kernel/cpufreq/Kconfig"
  530. endmenu
  531. menu "Bus options (PCI etc.)"
  532. config PCI
  533. bool "PCI support"
  534. # x86-64 doesn't support PCI BIOS access from long mode so always go direct.
  535. config PCI_DIRECT
  536. bool
  537. depends on PCI
  538. default y
  539. config PCI_MMCONFIG
  540. bool "Support mmconfig PCI config space access"
  541. depends on PCI && ACPI
  542. source "drivers/pci/pcie/Kconfig"
  543. source "drivers/pci/Kconfig"
  544. source "drivers/pcmcia/Kconfig"
  545. source "drivers/pci/hotplug/Kconfig"
  546. endmenu
  547. menu "Executable file formats / Emulations"
  548. source "fs/Kconfig.binfmt"
  549. config IA32_EMULATION
  550. bool "IA32 Emulation"
  551. help
  552. Include code to run 32-bit programs under a 64-bit kernel. You should likely
  553. turn this on, unless you're 100% sure that you don't have any 32-bit programs
  554. left.
  555. config IA32_AOUT
  556. tristate "IA32 a.out support"
  557. depends on IA32_EMULATION
  558. help
  559. Support old a.out binaries in the 32bit emulation.
  560. config COMPAT
  561. bool
  562. depends on IA32_EMULATION
  563. default y
  564. config SYSVIPC_COMPAT
  565. bool
  566. depends on COMPAT && SYSVIPC
  567. default y
  568. endmenu
  569. source "net/Kconfig"
  570. source drivers/Kconfig
  571. source "drivers/firmware/Kconfig"
  572. source fs/Kconfig
  573. menu "Instrumentation Support"
  574. depends on EXPERIMENTAL
  575. source "arch/x86_64/oprofile/Kconfig"
  576. config KPROBES
  577. bool "Kprobes (EXPERIMENTAL)"
  578. depends on KALLSYMS && EXPERIMENTAL && MODULES
  579. help
  580. Kprobes allows you to trap at almost any kernel address and
  581. execute a callback function. register_kprobe() establishes
  582. a probepoint and specifies the callback. Kprobes is useful
  583. for kernel debugging, non-intrusive instrumentation and testing.
  584. If in doubt, say "N".
  585. endmenu
  586. source "arch/x86_64/Kconfig.debug"
  587. source "security/Kconfig"
  588. source "crypto/Kconfig"
  589. source "lib/Kconfig"