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
30 prompt "IA-64 processor type"
36 Select your IA-64 processor type. The default is Intel Itanium.
37 This choice is safe for all IA-64 systems, but may not perform
38 optimally on systems with, say, Itanium 2 or newer processors.
43 Select this to configure for an Itanium 2 (McKinley) processor.
48 prompt "IA-64 system type"
54 This selects the system type of your hardware. A "generic" kernel
55 will run on any supported IA-64 system. However, if you configure
56 a kernel for your specific system, it will be faster and smaller.
58 To find out what type of IA-64 system you have, you may want to
59 check the IA-64 Linux web site at <http://www.linux-ia64.org/>.
60 As of the time of this writing, most hardware is DIG compliant,
61 so the "DIG-compliant" option is usually the right choice.
63 HP-simulator For the HP simulator
64 (<http://software.hp.com/ia64linux/>).
65 HP-zx1 For HP zx1-based systems.
66 SN1-simulator For the SGI SN1 simulator.
67 DIG-compliant For DIG ("Developer's Interface Guide") compliant
70 If you don't know what to do, choose "generic".
81 Build a kernel that runs on HP zx1-based systems. This adds support
82 for the zx1 I/O MMU and makes root bus bridges appear in PCI config
83 space (required for zx1 agpgart support).
94 prompt "Kernel page size"
95 default IA64_PAGE_SIZE_16KB
97 config IA64_PAGE_SIZE_4KB
100 This lets you select the page size of the kernel. For best IA-64
101 performance, a page size of 8KB or 16KB is recommended. For best
102 IA-32 compatibility, a page size of 4KB should be selected (the vast
103 majority of IA-32 binaries work perfectly fine with a larger page
104 size). For Itanium 2 or newer systems, a page size of 64KB can also
107 4KB For best IA-32 compatibility
108 8KB For best IA-64 performance
109 16KB For best IA-64 performance
110 64KB Requires Itanium 2 or newer processor.
112 If you don't know what to do, choose 16KB.
114 config IA64_PAGE_SIZE_8KB
117 config IA64_PAGE_SIZE_16KB
120 config IA64_PAGE_SIZE_64KB
128 depends on !IA64_HP_SIM
131 ACPI/OSPM support for Linux is currently under development. As such,
132 this support is preliminary and EXPERIMENTAL. Configuring ACPI
133 support enables kernel interfaces that allow higher level software
134 (OSPM) to manipulate ACPI defined hardware and software interfaces,
135 including the evaluation of ACPI control methods. If unsure, choose
136 N here. Note, this option will enlarge your kernel by about 120K.
138 This support requires an ACPI compliant platform (hardware/firmware).
139 If both ACPI and Advanced Power Management (APM) support are
140 configured, whichever is loaded first shall be used.
142 This code DOES NOT currently provide a complete OSPM implementation
143 -- it has not yet reached APM's level of functionality. When fully
144 implemented, Linux ACPI/OSPM will provide a more robust functional
145 replacement for legacy configuration and power management
146 interfaces, including the Plug-and-Play BIOS specification (PnP
147 BIOS), the Multi-Processor Specification (MPS), and the Advanced
148 Power Management specification (APM).
150 Linux support for ACPI/OSPM is based on Intel Corporation's ACPI
151 Component Architecture (ACPI CA). The latest ACPI CA source code,
152 documentation, debug builds, and implementation status information
153 can be downloaded from:
154 <http://developer.intel.com/technology/iapc/acpi/downloads.htm>.
156 The ACPI Sourceforge project may also be of interest:
157 <http://sf.net/projects/acpi/>
161 depends on !IA64_HP_SIM
164 config ACPI_INTERPRETER
166 depends on !IA64_HP_SIM
169 config ACPI_KERNEL_CONFIG
171 depends on !IA64_HP_SIM
174 If you say `Y' here, Linux's ACPI support will use the
175 hardware-level system descriptions found on IA-64 systems.
182 config ITANIUM_BSTEP_SPECIFIC
183 bool "Enable Itanium B-step specific code"
186 Select this option to build a kernel for an Itanium prototype system
187 with a B-step CPU. You have a B-step CPU if the "revision" field in
188 /proc/cpuinfo has a value in the range from 1 to 4.
190 # align cache-sensitive data to 128 bytes
191 config IA64_L1_CACHE_SHIFT
193 default "7" if MCKINLEY || ITANIUM && IA64_SGI_SN1
194 default "6" if ITANIUM && !IA64_SGI_SN1
196 # align cache-sensitive data to 64 bytes
197 config MCKINLEY_ASTEP_SPECIFIC
198 bool "Enable McKinley A-step specific code"
201 Select this option to build a kernel for an IA-64 McKinley prototype
202 system with any A-stepping CPU.
204 config MCKINLEY_A0_SPECIFIC
205 bool "Enable McKinley A0/A1-step specific code"
206 depends on MCKINLEY_ASTEP_SPECIFIC
208 Select this option to build a kernel for an IA-64 McKinley prototype
209 system with an A0 or A1 stepping CPU.
212 bool "Enable NUMA support" if IA64_GENERIC || IA64_DIG || IA64_HP_ZX1
213 default y if IA64_SGI_SN1 || IA64_SGI_SN2
215 Say Y to compile the kernel to support NUMA (Non-Uniform Memory
216 Access). This option is for configuring high-end multiprocessor
217 server systems. If in doubt, say N.
220 prompt "Maximum Memory per NUMA Node" if NUMA && IA64_DIG
221 depends on NUMA && IA64_DIG
222 default IA64_NODESIZE_16GB
224 config IA64_NODESIZE_16GB
227 config IA64_NODESIZE_64GB
230 config IA64_NODESIZE_256GB
237 depends on IA64_SGI_SN1 || IA64_SGI_SN2 || (IA64_GENERIC || IA64_DIG || IA64_HP_ZX1) && NUMA
240 Say Y to support efficient handling of discontiguous physical memory,
241 for architectures which are either NUMA (Non-Uniform Memory Access)
242 or have huge holes in the physical address space for other reasons.
243 See <file:Documentation/vm/numa> for more.
245 config VIRTUAL_MEM_MAP
246 bool "Enable Virtual Mem Map"
248 default y if IA64_GENERIC || IA64_DIG || IA64_HP_ZX1
250 Say Y to compile the kernel with support for a virtual mem map.
251 This is an alternate method of supporting large holes in the
252 physical address space on non NUMA machines. Since the DISCONTIGMEM
253 option is not supported on machines with the ZX1 chipset, this is
254 the only way of supporting more than 1 Gb of memory on those
255 machines. This code also only takes effect if a memory hole of
256 greater than 1 Gb is found during boot, so it is safe to enable
257 unless you require the DISCONTIGMEM option for your machine. If you
261 bool "Enable IA-64 Machine Check Abort" if IA64_GENERIC || IA64_DIG || IA64_HP_ZX1
262 default y if IA64_SGI_SN1 || IA64_SGI_SN2
264 Say Y here to enable machine check support for IA-64. If you're
269 depends on IA64_GENERIC || IA64_DIG || IA64_HP_ZX1
272 "Power Management" means that parts of your computer are shut
273 off or put into a power conserving "sleep" mode if they are not
274 being used. There are two competing standards for doing this: APM
275 and ACPI. If you want to use either one, say Y here and then also
276 to the requisite support below.
278 Power Management is most important for battery powered laptop
279 computers; if you have a laptop, check out the Linux Laptop home
281 <http://www.cs.utexas.edu/users/kharker/linux-laptop/> and the
282 Battery Powered Linux mini-HOWTO, available from
283 <http://www.tldp.org/docs.html#howto>.
285 Note that, even if you say N here, Linux on the x86 architecture
286 will issue the hlt instruction if nothing is to be done, thereby
287 sending the processor to sleep and saving power.
291 depends on IA64_GENERIC || IA64_DIG || IA64_HP_ZX1
296 depends on IA64_SGI_SN1 || IA64_SGI_SN2
299 config IA64_SGI_SN_DEBUG
300 bool "Enable extra debugging code"
301 depends on IA64_SGI_SN1 || IA64_SGI_SN2
303 Turns on extra debugging code in the SGI SN (Scalable NUMA) platform
304 for IA-64. Unless you are debugging problems on an SGI SN IA-64 box,
307 config IA64_SGI_SN_SIM
308 bool "Enable SGI Medusa Simulator Support"
309 depends on IA64_SGI_SN1 || IA64_SGI_SN2
311 If you are compiling a kernel that will run under SGI's IA-64
312 simulator (Medusa) then say Y, otherwise say N.
314 config IA64_SGI_AUTOTEST
315 bool "Enable autotest (llsc). Option to run cache test instead of booting"
316 depends on IA64_SGI_SN1 || IA64_SGI_SN2
318 Build a kernel used for hardware validation. If you include the
319 keyword "autotest" on the boot command line, the kernel does NOT boot.
320 Instead, it starts all cpus and runs cache coherency tests instead.
324 config SERIAL_SGI_L1_PROTOCOL
325 bool "Enable protocol mode for the L1 console"
326 depends on IA64_SGI_SN1 || IA64_SGI_SN2
328 Uses protocol mode instead of raw mode for the level 1 console on the
329 SGI SN (Scalable NUMA) platform for IA-64. If you are compiling for
330 an SGI SN box then Y is the recommended value, otherwise say N.
334 depends on IA64_SGI_SN1 || IA64_SGI_SN2
338 tristate "PCIBA support"
339 depends on IA64_SGI_SN1 || IA64_SGI_SN2
341 IRIX PCIBA-inspired user mode PCI interface for the SGI SN (Scalable
342 NUMA) platform for IA-64. Unless you are compiling a kernel for an
343 SGI SN IA-64 box, say N.
345 # On IA-64, we always want an ELF /proc/kcore.
350 If you enabled support for /proc file system then the file
351 /proc/kcore will contain the kernel core image. This can be used
354 $ cd /usr/src/linux ; gdb vmlinux /proc/kcore
356 You have two choices here: ELF and A.OUT. Selecting ELF will make
357 /proc/kcore appear in ELF core format as defined by the Executable
358 and Linking Format specification. Selecting A.OUT will choose the
359 old "a.out" format which may be necessary for some old versions
360 of binutils or on some architectures.
362 This is especially useful if you have compiled the kernel with the
363 "-g" option to preserve debugging information. It is mainly used
364 for examining kernel data structures on the live kernel so if you
365 don't understand what this means or are not a kernel hacker, just
366 leave it at its default value ELF.
368 config FORCE_MAX_ZONEORDER
373 bool "IA-64 Huge TLB Page Support"
376 prompt "IA-64 Huge TLB Page Size"
377 depends on HUGETLB_PAGE
378 default HUGETLB_PAGE_SIZE_16MB
380 config HUGETLB_PAGE_SIZE_4GB
384 config HUGETLB_PAGE_SIZE_256MB
387 config HUGETLB_PAGE_SIZE_64MB
390 config HUGETLB_PAGE_SIZE_16MB
393 config HUGETLB_PAGE_SIZE_4MB
396 config HUGETLB_PAGE_SIZE_1MB
399 config HUGETLB_PAGE_SIZE_256KB
405 bool "Use PAL_HALT_LIGHT in idle loop"
407 Say Y here to enable use of PAL_HALT_LIGHT in the cpu_idle loop.
408 This allows the CPU to enter a low power state when idle. You
409 can enable CONFIG_IA64_PALINFO and check /proc/pal/cpu0/power_info
410 to see the power consumption and latency for this state. If you're
411 unsure your firmware supports it, answer N.
416 This enables support for systems with more than one CPU. If you have
417 a system with only one CPU say N. If you have a system with more than
420 If you say N here, the kernel will run on single and multiprocessor
421 systems, but will use only one CPU of a multiprocessor system. If
422 you say Y here, the kernel will run on many, but not all,
423 singleprocessor system. On a singleprocessor system, the kernel
424 will run faster if you say N here.
426 See also the <file:Documentation/smp.tex>,
427 <file:Documentation/smp.txt>, and the SMP-HOWTO available at
428 <http://www.tldp.org/docs.html#howto>.
430 If you don't know what to do here, say N.
433 bool "Preemptible Kernel"
435 This option reduces the latency of the kernel when reacting to
436 real-time or interactive events by allowing a low priority process to
437 be preempted even if it is in kernel mode executing a system call.
438 This allows applications to run more reliably even when the system is
441 Say Y here if you are building a kernel for a desktop, embedded
442 or real-time system. Say N if you are unsure.
445 bool "Support running of Linux/x86 binaries"
447 IA-64 processors can execute IA-32 (X86) instructions. By
448 saying Y here, the kernel will include IA-32 system call
449 emulation support which makes it possible to transparently
450 run IA-32 Linux binaries on an IA-64 Linux system.
455 depends on IA32_SUPPORT
459 bool "Performance monitor support"
461 Selects whether support for the IA-64 performance monitor hardware
462 is included in the kernel. This makes some kernel data-structures a
463 little bigger and slows down execution a bit, but it is generally
464 a good idea to turn this on. If you're unsure, say Y.
467 tristate "/proc/pal support"
469 If you say Y here, you are able to get PAL (Processor Abstraction
470 Layer) information in /proc/pal. This contains useful information
471 about the processors in your systems, such as cache and TLB sizes
472 and the PAL firmware version in use.
474 To use this option, you have to ensure that the "/proc file system
475 support" (CONFIG_PROC_FS) is enabled, too.
478 tristate "/proc/efi/vars support"
480 If you say Y here, you are able to get EFI (Extensible Firmware
481 Interface) variable information in /proc/efi/vars. You may read,
482 write, create, and destroy EFI variables through this interface.
484 To use this option, you have to check that the "/proc file system
485 support" (CONFIG_PROC_FS) is enabled, too.
488 int "Maximum number of CPUs (2-64)"
493 tristate "Kernel support for ELF binaries"
495 ELF (Executable and Linkable Format) is a format for libraries and
496 executables used across different architectures and operating
497 systems. Saying Y here will enable your kernel to run ELF binaries.
499 Information about ELF is contained in the ELF HOWTO available from
500 <http://www.tldp.org/docs.html#howto>.
503 tristate "Kernel support for MISC binaries"
505 If you say Y here, it will be possible to plug wrapper-driven binary
506 formats into the kernel. You will like this especially when you use
507 programs that need an interpreter to run like Java, Python or
508 Emacs-Lisp. Once you have registered such a binary class with the
509 kernel, you can start one of those programs simply by typing in its
510 name at a shell prompt; Linux will automatically feed it to the
513 You can do other nice things, too. Read the file
514 <file:Documentation/binfmt_misc.txt> to learn how to use this
515 feature, and <file:Documentation/java.txt> for information about how
516 to include Java support.
518 You must say Y to "/proc file system support" (CONFIG_PROC_FS) to
519 use this part of the kernel.
521 You may say M here for module support and later load the module when
522 you have use for it; the module is called binfmt_misc. If you
523 don't know what to answer at this point, say Y.
527 source "drivers/acpi/Kconfig"
532 Find out whether you have a PCI motherboard. PCI is the name of a
533 bus system, i.e. the way the CPU talks to the other stuff inside
534 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
535 VESA. If you have PCI, say Y, otherwise N.
537 The PCI-HOWTO, available from
538 <http://www.tldp.org/docs.html#howto>, contains valuable
539 information about which PCI hardware does work under Linux and which
542 source "drivers/pci/Kconfig"
545 bool "Support for hot-pluggable devices"
547 Say Y here if you want to plug devices into your computer while
548 the system is running, and be able to use them quickly. In many
549 cases, the devices can likewise be unplugged at any time too.
551 One well known example of this is PCMCIA- or PC-cards, credit-card
552 size devices such as network cards, modems or hard drives which are
553 plugged into slots found on all modern laptop computers. Another
554 example, used on modern desktops as well as laptops, is USB.
556 Enable HOTPLUG and KMOD, and build a modular kernel. Get agent
557 software (at <http://linux-hotplug.sourceforge.net/>) and install it.
558 Then your kernel will automatically call out to a user mode "policy
559 agent" (/sbin/hotplug) to load modules and set up software needed
560 to use devices as you hotplug them.
562 source "drivers/hotplug/Kconfig"
564 source "drivers/pcmcia/Kconfig"
566 source "drivers/parport/Kconfig"
574 source "drivers/mtd/Kconfig"
576 source "drivers/pnp/Kconfig"
578 source "drivers/block/Kconfig"
580 source "drivers/ieee1394/Kconfig"
582 source "drivers/message/i2o/Kconfig"
584 source "drivers/md/Kconfig"
586 source "drivers/message/fusion/Kconfig"
589 menu "ATA/ATAPI/MFM/RLL support"
592 tristate "ATA/ATAPI/MFM/RLL support"
594 If you say Y here, your kernel will be able to manage low cost mass
595 storage units such as ATA/(E)IDE and ATAPI units. The most common
596 cases are IDE hard drives and ATAPI CD-ROM drives.
598 If your system is pure SCSI and doesn't use these interfaces, you
601 Integrated Disk Electronics (IDE aka ATA-1) is a connecting standard
602 for mass storage units such as hard disks. It was designed by
603 Western Digital and Compaq Computer in 1984. It was then named
604 ST506. Quite a number of disks use the IDE interface.
606 AT Attachment (ATA) is the superset of the IDE specifications.
607 ST506 was also called ATA-1.
609 Fast-IDE is ATA-2 (also named Fast ATA), Enhanced IDE (EIDE) is
610 ATA-3. It provides support for larger disks (up to 8.4GB by means of
611 the LBA standard), more disks (4 instead of 2) and for other mass
612 storage units such as tapes and cdrom. UDMA/33 (aka UltraDMA/33) is
613 ATA-4 and provides faster (and more CPU friendly) transfer modes
614 than previous PIO (Programmed processor Input/Output) from previous
615 ATA/IDE standards by means of fast DMA controllers.
617 ATA Packet Interface (ATAPI) is a protocol used by EIDE tape and
618 CD-ROM drives, similar in many respects to the SCSI protocol.
620 SMART IDE (Self Monitoring, Analysis and Reporting Technology) was
621 designed in order to prevent data corruption and disk crash by
622 detecting pre hardware failure conditions (heat, access time, and
623 the like...). Disks built since June 1995 may follow this standard.
624 The kernel itself don't manage this; however there are quite a
625 number of user programs such as smart that can query the status of
626 SMART parameters disk.
628 If you want to compile this driver as a module ( = code which can be
629 inserted in and removed from the running kernel whenever you want),
630 say M here and read <file:Documentation/modules.txt>. The module
633 For further information, please read <file:Documentation/ide.txt>.
637 source "drivers/ide/Kconfig"
647 tristate "SCSI support"
649 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
650 any other SCSI device under Linux, say Y and make sure that you know
651 the name of your SCSI host adapter (the card inside your computer
652 that "speaks" the SCSI protocol, also called SCSI controller),
653 because you will be asked for it.
655 You also need to say Y here if you want support for the parallel
656 port version of the 100 MB IOMEGA ZIP drive.
658 This driver is also available as a module ( = code which can be
659 inserted in and removed from the running kernel whenever you want).
660 The module will be called scsi_mod. If you want to compile it as
661 a module, say M here and read <file:Documentation/modules.txt> and
662 <file:Documentation/scsi/scsi.txt>. However, do not compile this as a
663 module if your root file system (the one containing the directory /)
664 is located on a SCSI device.
666 source "drivers/scsi/Kconfig"
675 source "net/ax25/Kconfig"
677 source "drivers/isdn/Kconfig"
680 menu "CD-ROM drivers (not for SCSI or IDE/ATAPI drives)"
683 bool "Support non-SCSI/IDE/ATAPI CDROM drives"
685 If you have a CD-ROM drive that is neither SCSI nor IDE/ATAPI, say Y
686 here, otherwise N. Read the CD-ROM-HOWTO, available from
687 <http://www.tldp.org/docs.html#howto>.
689 Note that the answer to this question doesn't directly affect the
690 kernel: saying N will just cause the configurator to skip all
691 the questions about these CD-ROM drives. If you are unsure what you
692 have, say Y and find out whether you have one of the following
695 For each of these drivers, a file Documentation/cdrom/{driver_name}
696 exists. Especially in cases where you do not know exactly which kind
697 of drive you have you should read there. Most of these drivers use a
698 file drivers/cdrom/{driver_name}.h where you can define your
699 interface parameters and switch some internal goodies.
701 All these CD-ROM drivers are also usable as a module ( = code which
702 can be inserted in and removed from the running kernel whenever you
703 want). If you want to compile them as module, say M instead of Y and
704 read <file:Documentation/modules.txt>.
706 If you want to use any of these CD-ROM drivers, you also have to
707 answer Y or M to "ISO 9660 CD-ROM file system support" below (this
708 answer will get "defaulted" for you if you enable any of the Linux
711 source "drivers/cdrom/Kconfig"
716 # input before char - char/joystick depends on it. As does USB.
718 source "drivers/input/Kconfig"
720 source "drivers/char/Kconfig"
722 #source drivers/misc/Config.in
723 source "drivers/media/Kconfig"
729 depends on IA64_HP_SIM
732 tristate "Loopback device support"
735 tristate "Network block device support"
739 tristate "RAM disk support"
741 config BLK_DEV_RAM_SIZE
742 int "Default RAM disk size"
743 depends on BLK_DEV_RAM
752 source "drivers/video/Kconfig"
757 tristate "Sound card support"
759 If you have a sound card in your computer, i.e. if it can say more
760 than an occasional beep, say Y. Be sure to have all the information
761 about your sound card and its configuration down (I/O port,
762 interrupt and DMA channel), because you will be asked for it.
764 You want to read the Sound-HOWTO, available from
765 <http://www.tldp.org/docs.html#howto>. General information about
766 the modular sound system is contained in the files
767 <file:Documentation/sound/Introduction>. The file
768 <file:Documentation/sound/README.OSS> contains some slightly
769 outdated but still useful information as well.
771 source "sound/Kconfig"
775 source "drivers/usb/Kconfig"
779 source "net/bluetooth/Kconfig"
783 source "arch/ia64/hp/sim/Kconfig"
786 menu "Kernel hacking"
789 bool "Light-weight system-call support (via epc)"
792 prompt "Physical memory granularity"
793 default IA64_GRANULE_64MB
795 config IA64_GRANULE_16MB
798 IA-64 identity-mapped regions use a large page size called "granules".
800 Select "16MB" for a small granule size.
801 Select "64MB" for a large granule size. This is the current default.
803 config IA64_GRANULE_64MB
809 bool "Kernel debugging"
811 Say Y here if you are developing drivers or trying to debug and
812 identify kernel problems.
815 bool "Load all symbols for debugging/kksymoops"
816 depends on DEBUG_KERNEL
818 Say Y here to let the kernel print out symbolic crash information and
819 symbolic stack backtraces. This increases the size of the kernel
820 somewhat, as all symbols have to be loaded into the kernel image.
822 config IA64_PRINT_HAZARDS
823 bool "Print possible IA-64 dependency violations to console"
824 depends on DEBUG_KERNEL
826 Selecting this option prints more information for Illegal Dependency
827 Faults, that is, for Read-after-Write (RAW), Write-after-Write (WAW),
828 or Write-after-Read (WAR) violations. This option is ignored if you
829 are compiling for an Itanium A step processor
830 (CONFIG_ITANIUM_ASTEP_SPECIFIC). If you're unsure, select Y.
834 depends on DEBUG_KERNEL
836 The Virtual Hash Page Table (VHPT) enhances virtual address
837 translation performance. Normally you want the VHPT active but you
838 can select this option to disable the VHPT for debugging. If you're
842 bool "Magic SysRq key"
843 depends on DEBUG_KERNEL
845 If you say Y here, you will have some control over the system even
846 if the system crashes for example during kernel debugging (e.g., you
847 will be able to flush the buffer cache to disk, reboot the system
848 immediately or dump some status information). This is accomplished
849 by pressing various keys while holding SysRq (Alt+PrintScreen). It
850 also works on a serial console (on PC hardware at least), if you
851 send a BREAK and then within 5 seconds a command keypress. The
852 keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
853 unless you really know what this hack does.
855 config IA64_EARLY_PRINTK
856 bool "Early printk support"
857 depends on DEBUG_KERNEL
859 Selecting this option uses the VGA screen or serial console for
860 printk() output before the consoles are initialised. It is useful
861 for debugging problems early in the boot process, but only if you
862 have a suitable VGA/serial console attached. If you're unsure,
865 config IA64_EARLY_PRINTK_UART
866 bool "Early printk on MMIO serial port"
867 depends on IA64_EARLY_PRINTK
869 config IA64_EARLY_PRINTK_UART_BASE
870 hex "UART MMIO base address"
871 depends on IA64_EARLY_PRINTK_UART
874 config IA64_EARLY_PRINTK_VGA
875 bool "Early printk on VGA"
876 depends on IA64_EARLY_PRINTK
879 bool "Debug memory allocations"
880 depends on DEBUG_KERNEL
882 Say Y here to have the kernel do limited verification on memory
883 allocation as well as poisoning memory on free to catch use of freed
886 config DEBUG_SPINLOCK
887 bool "Spinlock debugging"
888 depends on DEBUG_KERNEL
890 Say Y here and build SMP to catch missing spinlock initialization
891 and certain other kinds of spinlock errors commonly made. This is
892 best used in conjunction with the NMI watchdog so that spinlock
893 deadlocks are also debuggable.
895 config DEBUG_SPINLOCK_SLEEP
896 bool "Sleep-inside-spinlock checking"
898 If you say Y here, various routines which may sleep will become very
899 noisy if they are called with a spinlock held.
901 config IA64_DEBUG_CMPXCHG
902 bool "Turn on compare-and-exchange bug checking (slow!)"
903 depends on DEBUG_KERNEL
905 Selecting this option turns on bug checking for the IA-64
906 compare-and-exchange instructions. This is slow! Itaniums
907 from step B3 or later don't have this problem. If you're unsure,
910 config IA64_DEBUG_IRQ
911 bool "Turn on irq debug checks (slow!)"
912 depends on DEBUG_KERNEL
914 Selecting this option turns on bug checking for the IA-64 irq_save
915 and restore instructions. It's useful for tracking down spinlock
916 problems, but slow! If you're unsure, select N.
920 source "security/Kconfig"
922 source "crypto/Kconfig"
924 source "rpmify/Kconfig"