arch/x86_64/Kconfig

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