2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
6 mainmenu "IA-64 Linux Kernel Configuration"
10 menu "Processor type and features"
16 The Itanium Processor Family is Intel's 64-bit successor to
17 the 32-bit X86 line. The IA-64 Linux project has a home
18 page at <http://www.linuxia64.org/> and a mailing list at
19 linux-ia64@linuxia64.org.
25 config RWSEM_XCHGADD_ALGORITHM
29 config TIME_INTERPOLATION
34 prompt "IA-64 processor type"
40 Select your IA-64 processor type. The default is Intel Itanium.
41 This choice is safe for all IA-64 systems, but may not perform
42 optimally on systems with, say, Itanium 2 or newer processors.
47 Select this to configure for an Itanium 2 (McKinley) processor.
52 prompt "IA-64 system type"
58 This selects the system type of your hardware. A "generic" kernel
59 will run on any supported IA-64 system. However, if you configure
60 a kernel for your specific system, it will be faster and smaller.
62 To find out what type of IA-64 system you have, you may want to
63 check the IA-64 Linux web site at <http://www.linux-ia64.org/>.
64 As of the time of this writing, most hardware is DIG compliant,
65 so the "DIG-compliant" option is usually the right choice.
67 HP-simulator For the HP simulator
68 (<http://software.hp.com/ia64linux/>).
69 HP-zx1 For HP zx1-based systems.
70 SGI-SN2 For SGI Altix systems
71 DIG-compliant For DIG ("Developer's Interface Guide") compliant
74 If you don't know what to do, choose "generic".
85 Build a kernel that runs on HP zx1-based systems. This adds support
86 for the zx1 I/O MMU and makes root bus bridges appear in PCI config
87 space (required for zx1 agpgart support).
95 prompt "Kernel page size"
96 default IA64_PAGE_SIZE_16KB
98 config IA64_PAGE_SIZE_4KB
101 This lets you select the page size of the kernel. For best IA-64
102 performance, a page size of 8KB or 16KB is recommended. For best
103 IA-32 compatibility, a page size of 4KB should be selected (the vast
104 majority of IA-32 binaries work perfectly fine with a larger page
105 size). For Itanium 2 or newer systems, a page size of 64KB can also
108 4KB For best IA-32 compatibility
109 8KB For best IA-64 performance
110 16KB For best IA-64 performance
111 64KB Requires Itanium 2 or newer processor.
113 If you don't know what to do, choose 16KB.
115 config IA64_PAGE_SIZE_8KB
118 config IA64_PAGE_SIZE_16KB
121 config IA64_PAGE_SIZE_64KB
129 depends on !IA64_HP_SIM
132 ACPI/OSPM support for Linux is currently under development. As such,
133 this support is preliminary and EXPERIMENTAL. Configuring ACPI
134 support enables kernel interfaces that allow higher level software
135 (OSPM) to manipulate ACPI defined hardware and software interfaces,
136 including the evaluation of ACPI control methods. If unsure, choose
137 N here. Note, this option will enlarge your kernel by about 120K.
139 This support requires an ACPI compliant platform (hardware/firmware).
140 If both ACPI and Advanced Power Management (APM) support are
141 configured, whichever is loaded first shall be used.
143 This code DOES NOT currently provide a complete OSPM implementation
144 -- it has not yet reached APM's level of functionality. When fully
145 implemented, Linux ACPI/OSPM will provide a more robust functional
146 replacement for legacy configuration and power management
147 interfaces, including the Plug-and-Play BIOS specification (PnP
148 BIOS), the Multi-Processor Specification (MPS), and the Advanced
149 Power Management specification (APM).
151 Linux support for ACPI/OSPM is based on Intel Corporation's ACPI
152 Component Architecture (ACPI CA). The latest ACPI CA source code,
153 documentation, debug builds, and implementation status information
154 can be downloaded from:
155 <http://developer.intel.com/technology/iapc/acpi/downloads.htm>.
157 The ACPI Sourceforge project may also be of interest:
158 <http://sf.net/projects/acpi/>
162 depends on !IA64_HP_SIM
165 config ACPI_INTERPRETER
167 depends on !IA64_HP_SIM
170 config ACPI_KERNEL_CONFIG
172 depends on !IA64_HP_SIM
175 If you say `Y' here, Linux's ACPI support will use the
176 hardware-level system descriptions found on IA-64 systems.
183 config ITANIUM_BSTEP_SPECIFIC
184 bool "Enable Itanium B-step specific code"
187 Select this option to build a kernel for an Itanium prototype system
188 with a B-step CPU. You have a B-step CPU if the "revision" field in
189 /proc/cpuinfo has a value in the range from 1 to 4.
191 # align cache-sensitive data to 128 bytes
192 config IA64_L1_CACHE_SHIFT
194 default "7" if MCKINLEY
195 default "6" if ITANIUM
197 # align cache-sensitive data to 64 bytes
198 config MCKINLEY_ASTEP_SPECIFIC
199 bool "Enable McKinley A-step specific code"
202 Select this option to build a kernel for an IA-64 McKinley prototype
203 system with any A-stepping CPU.
205 config MCKINLEY_A0_SPECIFIC
206 bool "Enable McKinley A0/A1-step specific code"
207 depends on MCKINLEY_ASTEP_SPECIFIC
209 Select this option to build a kernel for an IA-64 McKinley prototype
210 system with an A0 or A1 stepping CPU.
213 bool "Enable NUMA support" if IA64_GENERIC || IA64_DIG || IA64_HP_ZX1
214 default y if IA64_SGI_SN2
216 Say Y to compile the kernel to support NUMA (Non-Uniform Memory
217 Access). This option is for configuring high-end multiprocessor
218 server systems. If in doubt, say N.
221 prompt "Maximum Memory per NUMA Node" if NUMA && IA64_DIG
222 depends on NUMA && IA64_DIG
223 default IA64_NODESIZE_16GB
225 config IA64_NODESIZE_16GB
228 config IA64_NODESIZE_64GB
231 config IA64_NODESIZE_256GB
238 depends on IA64_SGI_SN2 || (IA64_GENERIC || IA64_DIG || IA64_HP_ZX1) && NUMA
241 Say Y to support efficient handling of discontiguous physical memory,
242 for architectures which are either NUMA (Non-Uniform Memory Access)
243 or have huge holes in the physical address space for other reasons.
244 See <file:Documentation/vm/numa> for more.
246 config VIRTUAL_MEM_MAP
247 bool "Enable Virtual Mem Map"
249 default y if IA64_GENERIC || IA64_DIG || IA64_HP_ZX1
251 Say Y to compile the kernel with support for a virtual mem map.
252 This is an alternate method of supporting large holes in the
253 physical address space on non NUMA machines. Since the DISCONTIGMEM
254 option is not supported on machines with the ZX1 chipset, this is
255 the only way of supporting more than 1 Gb of memory on those
256 machines. This code also only takes effect if a memory hole of
257 greater than 1 Gb is found during boot, so it is safe to enable
258 unless you require the DISCONTIGMEM option for your machine. If you
262 bool "Enable IA-64 Machine Check Abort" if IA64_GENERIC || IA64_DIG || IA64_HP_ZX1
263 default y if IA64_SGI_SN2
265 Say Y here to enable machine check support for IA-64. If you're
270 depends on IA64_GENERIC || IA64_DIG || IA64_HP_ZX1
273 "Power Management" means that parts of your computer are shut
274 off or put into a power conserving "sleep" mode if they are not
275 being used. There are two competing standards for doing this: APM
276 and ACPI. If you want to use either one, say Y here and then also
277 to the requisite support below.
279 Power Management is most important for battery powered laptop
280 computers; if you have a laptop, check out the Linux Laptop home
282 <http://www.cs.utexas.edu/users/kharker/linux-laptop/> and the
283 Battery Powered Linux mini-HOWTO, available from
284 <http://www.tldp.org/docs.html#howto>.
286 Note that, even if you say N here, Linux on the x86 architecture
287 will issue the hlt instruction if nothing is to be done, thereby
288 sending the processor to sleep and saving power.
292 depends on IA64_GENERIC || IA64_DIG || IA64_HP_ZX1 || IA64_SGI_SN2
297 depends on IA64_SGI_SN2
302 depends on IA64_SGI_SN2
305 config IA64_SGI_SN_DEBUG
306 bool "Enable extra debugging code"
307 depends on IA64_SGI_SN2
309 Turns on extra debugging code in the SGI SN (Scalable NUMA) platform
310 for IA-64. Unless you are debugging problems on an SGI SN IA-64 box,
313 config IA64_SGI_SN_SIM
314 bool "Enable SGI Medusa Simulator Support"
315 depends on IA64_SGI_SN2
317 If you are compiling a kernel that will run under SGI's IA-64
318 simulator (Medusa) then say Y, otherwise say N.
320 config IA64_SGI_AUTOTEST
321 bool "Enable autotest (llsc). Option to run cache test instead of booting"
322 depends on IA64_SGI_SN2
324 Build a kernel used for hardware validation. If you include the
325 keyword "autotest" on the boot command line, the kernel does NOT boot.
326 Instead, it starts all cpus and runs cache coherency tests instead.
330 config SERIAL_SGI_L1_PROTOCOL
331 bool "Enable protocol mode for the L1 console"
332 depends on IA64_SGI_SN2
334 Uses protocol mode instead of raw mode for the level 1 console on the
335 SGI SN (Scalable NUMA) platform for IA-64. If you are compiling for
336 an SGI SN box then Y is the recommended value, otherwise say N.
340 depends on IA64_SGI_SN2
344 tristate "PCIBA support"
345 depends on IA64_SGI_SN2
347 IRIX PCIBA-inspired user mode PCI interface for the SGI SN (Scalable
348 NUMA) platform for IA-64. Unless you are compiling a kernel for an
349 SGI SN IA-64 box, say N.
351 # On IA-64, we always want an ELF /proc/kcore.
356 If you enabled support for /proc file system then the file
357 /proc/kcore will contain the kernel core image. This can be used
360 $ cd /usr/src/linux ; gdb vmlinux /proc/kcore
362 You have two choices here: ELF and A.OUT. Selecting ELF will make
363 /proc/kcore appear in ELF core format as defined by the Executable
364 and Linking Format specification. Selecting A.OUT will choose the
365 old "a.out" format which may be necessary for some old versions
366 of binutils or on some architectures.
368 This is especially useful if you have compiled the kernel with the
369 "-g" option to preserve debugging information. It is mainly used
370 for examining kernel data structures on the live kernel so if you
371 don't understand what this means or are not a kernel hacker, just
372 leave it at its default value ELF.
374 config FORCE_MAX_ZONEORDER
379 bool "IA-64 Huge TLB Page Support"
382 prompt "IA-64 Huge TLB Page Size"
383 depends on HUGETLB_PAGE
384 default HUGETLB_PAGE_SIZE_16MB
386 config HUGETLB_PAGE_SIZE_4GB
390 config HUGETLB_PAGE_SIZE_1GB
394 config HUGETLB_PAGE_SIZE_256MB
397 config HUGETLB_PAGE_SIZE_64MB
400 config HUGETLB_PAGE_SIZE_16MB
403 config HUGETLB_PAGE_SIZE_4MB
406 config HUGETLB_PAGE_SIZE_1MB
409 config HUGETLB_PAGE_SIZE_256KB
415 bool "Use PAL_HALT_LIGHT in idle loop"
417 Say Y here to enable use of PAL_HALT_LIGHT in the cpu_idle loop.
418 This allows the CPU to enter a low power state when idle. You
419 can enable CONFIG_IA64_PALINFO and check /proc/pal/cpu0/power_info
420 to see the power consumption and latency for this state. If you're
421 unsure your firmware supports it, answer N.
426 This enables support for systems with more than one CPU. If you have
427 a system with only one CPU say N. If you have a system with more than
430 If you say N here, the kernel will run on single and multiprocessor
431 systems, but will use only one CPU of a multiprocessor system. If
432 you say Y here, the kernel will run on many, but not all,
433 singleprocessor system. On a singleprocessor system, the kernel
434 will run faster if you say N here.
436 See also the <file:Documentation/smp.tex>,
437 <file:Documentation/smp.txt>, and the SMP-HOWTO available at
438 <http://www.tldp.org/docs.html#howto>.
440 If you don't know what to do here, say N.
443 bool "Preemptible Kernel"
445 This option reduces the latency of the kernel when reacting to
446 real-time or interactive events by allowing a low priority process to
447 be preempted even if it is in kernel mode executing a system call.
448 This allows applications to run more reliably even when the system is
451 Say Y here if you are building a kernel for a desktop, embedded
452 or real-time system. Say N if you are unsure.
455 bool "Support running of Linux/x86 binaries"
457 IA-64 processors can execute IA-32 (X86) instructions. By
458 saying Y here, the kernel will include IA-32 system call
459 emulation support which makes it possible to transparently
460 run IA-32 Linux binaries on an IA-64 Linux system.
465 depends on IA32_SUPPORT
469 bool "Performance monitor support"
471 Selects whether support for the IA-64 performance monitor hardware
472 is included in the kernel. This makes some kernel data-structures a
473 little bigger and slows down execution a bit, but it is generally
474 a good idea to turn this on. If you're unsure, say Y.
477 tristate "/proc/pal support"
479 If you say Y here, you are able to get PAL (Processor Abstraction
480 Layer) information in /proc/pal. This contains useful information
481 about the processors in your systems, such as cache and TLB sizes
482 and the PAL firmware version in use.
484 To use this option, you have to ensure that the "/proc file system
485 support" (CONFIG_PROC_FS) is enabled, too.
488 tristate "/proc/efi/vars support"
490 If you say Y here, you are able to get EFI (Extensible Firmware
491 Interface) variable information in /proc/efi/vars. You may read,
492 write, create, and destroy EFI variables through this interface.
494 To use this option, you have to check that the "/proc file system
495 support" (CONFIG_PROC_FS) is enabled, too.
498 int "Maximum number of CPUs (2-64)"
503 tristate "Kernel support for ELF binaries"
505 ELF (Executable and Linkable Format) is a format for libraries and
506 executables used across different architectures and operating
507 systems. Saying Y here will enable your kernel to run ELF binaries.
509 Information about ELF is contained in the ELF HOWTO available from
510 <http://www.tldp.org/docs.html#howto>.
513 tristate "Kernel support for MISC binaries"
515 If you say Y here, it will be possible to plug wrapper-driven binary
516 formats into the kernel. You will like this especially when you use
517 programs that need an interpreter to run like Java, Python or
518 Emacs-Lisp. Once you have registered such a binary class with the
519 kernel, you can start one of those programs simply by typing in its
520 name at a shell prompt; Linux will automatically feed it to the
523 You can do other nice things, too. Read the file
524 <file:Documentation/binfmt_misc.txt> to learn how to use this
525 feature, and <file:Documentation/java.txt> for information about how
526 to include Java support.
528 You must say Y to "/proc file system support" (CONFIG_PROC_FS) to
529 use this part of the kernel.
531 You may say M here for module support and later load the module when
532 you have use for it; the module is called binfmt_misc. If you
533 don't know what to answer at this point, say Y.
537 source "drivers/acpi/Kconfig"
542 Find out whether you have a PCI motherboard. PCI is the name of a
543 bus system, i.e. the way the CPU talks to the other stuff inside
544 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
545 VESA. If you have PCI, say Y, otherwise N.
547 The PCI-HOWTO, available from
548 <http://www.tldp.org/docs.html#howto>, contains valuable
549 information about which PCI hardware does work under Linux and which
552 source "drivers/pci/Kconfig"
555 bool "Support for hot-pluggable devices"
557 Say Y here if you want to plug devices into your computer while
558 the system is running, and be able to use them quickly. In many
559 cases, the devices can likewise be unplugged at any time too.
561 One well known example of this is PCMCIA- or PC-cards, credit-card
562 size devices such as network cards, modems or hard drives which are
563 plugged into slots found on all modern laptop computers. Another
564 example, used on modern desktops as well as laptops, is USB.
566 Enable HOTPLUG and KMOD, and build a modular kernel. Get agent
567 software (at <http://linux-hotplug.sourceforge.net/>) and install it.
568 Then your kernel will automatically call out to a user mode "policy
569 agent" (/sbin/hotplug) to load modules and set up software needed
570 to use devices as you hotplug them.
572 source "drivers/hotplug/Kconfig"
574 source "drivers/pcmcia/Kconfig"
576 source "drivers/parport/Kconfig"
584 source "drivers/mtd/Kconfig"
586 source "drivers/pnp/Kconfig"
588 source "drivers/block/Kconfig"
590 source "drivers/ieee1394/Kconfig"
592 source "drivers/message/i2o/Kconfig"
594 source "drivers/md/Kconfig"
596 source "drivers/message/fusion/Kconfig"
599 menu "ATA/ATAPI/MFM/RLL support"
602 tristate "ATA/ATAPI/MFM/RLL support"
604 If you say Y here, your kernel will be able to manage low cost mass
605 storage units such as ATA/(E)IDE and ATAPI units. The most common
606 cases are IDE hard drives and ATAPI CD-ROM drives.
608 If your system is pure SCSI and doesn't use these interfaces, you
611 Integrated Disk Electronics (IDE aka ATA-1) is a connecting standard
612 for mass storage units such as hard disks. It was designed by
613 Western Digital and Compaq Computer in 1984. It was then named
614 ST506. Quite a number of disks use the IDE interface.
616 AT Attachment (ATA) is the superset of the IDE specifications.
617 ST506 was also called ATA-1.
619 Fast-IDE is ATA-2 (also named Fast ATA), Enhanced IDE (EIDE) is
620 ATA-3. It provides support for larger disks (up to 8.4GB by means of
621 the LBA standard), more disks (4 instead of 2) and for other mass
622 storage units such as tapes and cdrom. UDMA/33 (aka UltraDMA/33) is
623 ATA-4 and provides faster (and more CPU friendly) transfer modes
624 than previous PIO (Programmed processor Input/Output) from previous
625 ATA/IDE standards by means of fast DMA controllers.
627 ATA Packet Interface (ATAPI) is a protocol used by EIDE tape and
628 CD-ROM drives, similar in many respects to the SCSI protocol.
630 SMART IDE (Self Monitoring, Analysis and Reporting Technology) was
631 designed in order to prevent data corruption and disk crash by
632 detecting pre hardware failure conditions (heat, access time, and
633 the like...). Disks built since June 1995 may follow this standard.
634 The kernel itself don't manage this; however there are quite a
635 number of user programs such as smart that can query the status of
636 SMART parameters disk.
638 If you want to compile this driver as a module ( = code which can be
639 inserted in and removed from the running kernel whenever you want),
640 say M here and read <file:Documentation/modules.txt>. The module
643 For further information, please read <file:Documentation/ide.txt>.
647 source "drivers/ide/Kconfig"
657 tristate "SCSI support"
659 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
660 any other SCSI device under Linux, say Y and make sure that you know
661 the name of your SCSI host adapter (the card inside your computer
662 that "speaks" the SCSI protocol, also called SCSI controller),
663 because you will be asked for it.
665 You also need to say Y here if you want support for the parallel
666 port version of the 100 MB IOMEGA ZIP drive.
668 This driver is also available as a module ( = code which can be
669 inserted in and removed from the running kernel whenever you want).
670 The module will be called scsi_mod. If you want to compile it as
671 a module, say M here and read <file:Documentation/modules.txt> and
672 <file:Documentation/scsi/scsi.txt>. However, do not compile this as a
673 module if your root file system (the one containing the directory /)
674 is located on a SCSI device.
676 source "drivers/scsi/Kconfig"
685 source "net/ax25/Kconfig"
687 source "drivers/isdn/Kconfig"
690 menu "CD-ROM drivers (not for SCSI or IDE/ATAPI drives)"
693 bool "Support non-SCSI/IDE/ATAPI CDROM drives"
695 If you have a CD-ROM drive that is neither SCSI nor IDE/ATAPI, say Y
696 here, otherwise N. Read the CD-ROM-HOWTO, available from
697 <http://www.tldp.org/docs.html#howto>.
699 Note that the answer to this question doesn't directly affect the
700 kernel: saying N will just cause the configurator to skip all
701 the questions about these CD-ROM drives. If you are unsure what you
702 have, say Y and find out whether you have one of the following
705 For each of these drivers, a file Documentation/cdrom/{driver_name}
706 exists. Especially in cases where you do not know exactly which kind
707 of drive you have you should read there. Most of these drivers use a
708 file drivers/cdrom/{driver_name}.h where you can define your
709 interface parameters and switch some internal goodies.
711 All these CD-ROM drivers are also usable as a module ( = code which
712 can be inserted in and removed from the running kernel whenever you
713 want). If you want to compile them as module, say M instead of Y and
714 read <file:Documentation/modules.txt>.
716 If you want to use any of these CD-ROM drivers, you also have to
717 answer Y or M to "ISO 9660 CD-ROM file system support" below (this
718 answer will get "defaulted" for you if you enable any of the Linux
721 source "drivers/cdrom/Kconfig"
726 # input before char - char/joystick depends on it. As does USB.
728 source "drivers/input/Kconfig"
730 source "drivers/char/Kconfig"
732 #source drivers/misc/Config.in
733 source "drivers/media/Kconfig"
739 depends on IA64_HP_SIM
742 tristate "Loopback device support"
745 tristate "Network block device support"
749 tristate "RAM disk support"
751 config BLK_DEV_RAM_SIZE
752 int "Default RAM disk size"
753 depends on BLK_DEV_RAM
762 source "drivers/video/Kconfig"
767 tristate "Sound card support"
769 If you have a sound card in your computer, i.e. if it can say more
770 than an occasional beep, say Y. Be sure to have all the information
771 about your sound card and its configuration down (I/O port,
772 interrupt and DMA channel), because you will be asked for it.
774 You want to read the Sound-HOWTO, available from
775 <http://www.tldp.org/docs.html#howto>. General information about
776 the modular sound system is contained in the files
777 <file:Documentation/sound/Introduction>. The file
778 <file:Documentation/sound/README.OSS> contains some slightly
779 outdated but still useful information as well.
781 source "sound/Kconfig"
785 source "drivers/usb/Kconfig"
789 source "net/bluetooth/Kconfig"
793 source "arch/ia64/hp/sim/Kconfig"
796 menu "Kernel hacking"
799 bool "Light-weight system-call support (via epc)"
802 prompt "Physical memory granularity"
803 default IA64_GRANULE_64MB
805 config IA64_GRANULE_16MB
808 IA-64 identity-mapped regions use a large page size called "granules".
810 Select "16MB" for a small granule size.
811 Select "64MB" for a large granule size. This is the current default.
813 config IA64_GRANULE_64MB
819 bool "Kernel debugging"
821 Say Y here if you are developing drivers or trying to debug and
822 identify kernel problems.
825 bool "Load all symbols for debugging/kksymoops"
826 depends on DEBUG_KERNEL
828 Say Y here to let the kernel print out symbolic crash information and
829 symbolic stack backtraces. This increases the size of the kernel
830 somewhat, as all symbols have to be loaded into the kernel image.
832 config IA64_PRINT_HAZARDS
833 bool "Print possible IA-64 dependency violations to console"
834 depends on DEBUG_KERNEL
836 Selecting this option prints more information for Illegal Dependency
837 Faults, that is, for Read-after-Write (RAW), Write-after-Write (WAW),
838 or Write-after-Read (WAR) violations. This option is ignored if you
839 are compiling for an Itanium A step processor
840 (CONFIG_ITANIUM_ASTEP_SPECIFIC). If you're unsure, select Y.
844 depends on DEBUG_KERNEL
846 The Virtual Hash Page Table (VHPT) enhances virtual address
847 translation performance. Normally you want the VHPT active but you
848 can select this option to disable the VHPT for debugging. If you're
852 bool "Magic SysRq key"
853 depends on DEBUG_KERNEL
855 If you say Y here, you will have some control over the system even
856 if the system crashes for example during kernel debugging (e.g., you
857 will be able to flush the buffer cache to disk, reboot the system
858 immediately or dump some status information). This is accomplished
859 by pressing various keys while holding SysRq (Alt+PrintScreen). It
860 also works on a serial console (on PC hardware at least), if you
861 send a BREAK and then within 5 seconds a command keypress. The
862 keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
863 unless you really know what this hack does.
865 config IA64_EARLY_PRINTK
866 bool "Early printk support"
867 depends on DEBUG_KERNEL
869 Selecting this option uses the VGA screen or serial console for
870 printk() output before the consoles are initialised. It is useful
871 for debugging problems early in the boot process, but only if you
872 have a suitable VGA/serial console attached. If you're unsure,
875 config IA64_EARLY_PRINTK_UART
876 bool "Early printk on MMIO serial port"
877 depends on IA64_EARLY_PRINTK
879 config IA64_EARLY_PRINTK_UART_BASE
880 hex "UART MMIO base address"
881 depends on IA64_EARLY_PRINTK_UART
884 config IA64_EARLY_PRINTK_VGA
885 bool "Early printk on VGA"
886 depends on IA64_EARLY_PRINTK
889 bool "Debug memory allocations"
890 depends on DEBUG_KERNEL
892 Say Y here to have the kernel do limited verification on memory
893 allocation as well as poisoning memory on free to catch use of freed
896 config DEBUG_SPINLOCK
897 bool "Spinlock debugging"
898 depends on DEBUG_KERNEL
900 Say Y here and build SMP to catch missing spinlock initialization
901 and certain other kinds of spinlock errors commonly made. This is
902 best used in conjunction with the NMI watchdog so that spinlock
903 deadlocks are also debuggable.
905 config DEBUG_SPINLOCK_SLEEP
906 bool "Sleep-inside-spinlock checking"
908 If you say Y here, various routines which may sleep will become very
909 noisy if they are called with a spinlock held.
911 config IA64_DEBUG_CMPXCHG
912 bool "Turn on compare-and-exchange bug checking (slow!)"
913 depends on DEBUG_KERNEL
915 Selecting this option turns on bug checking for the IA-64
916 compare-and-exchange instructions. This is slow! Itaniums
917 from step B3 or later don't have this problem. If you're unsure,
920 config IA64_DEBUG_IRQ
921 bool "Turn on irq debug checks (slow!)"
922 depends on DEBUG_KERNEL
924 Selecting this option turns on bug checking for the IA-64 irq_save
925 and restore instructions. It's useful for tracking down spinlock
926 problems, but slow! If you're unsure, select N.
930 source "security/Kconfig"
932 source "crypto/Kconfig"
934 source "rpmify/Kconfig"