2005-04-16 18:20:36 -04:00
|
|
|
#
|
|
|
|
# For a description of the syntax of this configuration file,
|
|
|
|
# see Documentation/kbuild/kconfig-language.txt.
|
|
|
|
#
|
|
|
|
|
|
|
|
mainmenu "IA-64 Linux Kernel Configuration"
|
|
|
|
|
|
|
|
source "init/Kconfig"
|
|
|
|
|
|
|
|
menu "Processor type and features"
|
|
|
|
|
|
|
|
config IA64
|
|
|
|
bool
|
|
|
|
default y
|
|
|
|
help
|
|
|
|
The Itanium Processor Family is Intel's 64-bit successor to
|
|
|
|
the 32-bit X86 line. The IA-64 Linux project has a home
|
|
|
|
page at <http://www.linuxia64.org/> and a mailing list at
|
|
|
|
<linux-ia64@vger.kernel.org>.
|
|
|
|
|
|
|
|
config 64BIT
|
|
|
|
bool
|
|
|
|
default y
|
|
|
|
|
|
|
|
config MMU
|
|
|
|
bool
|
|
|
|
default y
|
|
|
|
|
2005-09-29 17:42:42 -04:00
|
|
|
config SWIOTLB
|
|
|
|
bool
|
|
|
|
default y
|
|
|
|
|
2005-04-16 18:20:36 -04:00
|
|
|
config RWSEM_XCHGADD_ALGORITHM
|
|
|
|
bool
|
|
|
|
default y
|
|
|
|
|
[PATCH] bitops: ia64: use generic bitops
- remove generic_fls64()
- remove find_{next,first}{,_zero}_bit()
- remove ext2_{set,clear,test,find_first_zero,find_next_zero}_bit()
- remove minix_{test,set,test_and_clear,test,find_first_zero}_bit()
- remove sched_find_first_bit()
Signed-off-by: Akinobu Mita <mita@miraclelinux.com>
Cc: "Luck, Tony" <tony.luck@intel.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-03-26 04:39:25 -05:00
|
|
|
config GENERIC_FIND_NEXT_BIT
|
|
|
|
bool
|
|
|
|
default y
|
|
|
|
|
2005-04-16 18:20:36 -04:00
|
|
|
config GENERIC_CALIBRATE_DELAY
|
|
|
|
bool
|
|
|
|
default y
|
|
|
|
|
|
|
|
config TIME_INTERPOLATION
|
|
|
|
bool
|
|
|
|
default y
|
|
|
|
|
[PATCH] ia64: use i386 dmi_scan.c
Enable DMI table parsing on ia64.
Andi Kleen has a patch in his x86_64 tree which enables the use of i386
dmi_scan.c on x86_64. dmi_scan.c functions are being used by the
drivers/char/ipmi/ipmi_si_intf.c driver for autodetecting the ports or
memory spaces where the IPMI controllers may be found.
This patch adds equivalent changes for ia64 as to what is in the x86_64
tree. In addition, I reworked the DMI detection, such that on EFI-capable
systems, it uses the efi.smbios pointer to find the table, rather than
brute-force searching from 0xF0000. On non-EFI systems, it continues the
brute-force search.
My test system, an Intel S870BN4 'Tiger4', aka Dell PowerEdge 7250, with
latest BIOS, does not list the IPMI controller in the ACPI namespace, nor
does it have an ACPI SPMI table. Also note, currently shipping Dell x8xx
EM64T servers don't have these either, so DMI is the only method for
obtaining the address of the IPMI controller.
Signed-off-by: Matt Domsch <Matt_Domsch@dell.com>
Acked-by: "Luck, Tony" <tony.luck@intel.com>
Cc: Andi Kleen <ak@muc.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-03-26 04:37:03 -05:00
|
|
|
config DMI
|
|
|
|
bool
|
|
|
|
default y
|
|
|
|
|
2005-04-16 18:20:36 -04:00
|
|
|
config EFI
|
|
|
|
bool
|
|
|
|
default y
|
|
|
|
|
|
|
|
config GENERIC_IOMAP
|
|
|
|
bool
|
|
|
|
default y
|
|
|
|
|
2005-05-05 19:15:11 -04:00
|
|
|
config SCHED_NO_NO_OMIT_FRAME_POINTER
|
|
|
|
bool
|
|
|
|
default y
|
|
|
|
|
2005-06-21 20:15:02 -04:00
|
|
|
config IA64_UNCACHED_ALLOCATOR
|
|
|
|
bool
|
|
|
|
select GENERIC_ALLOCATOR
|
|
|
|
|
2006-09-12 03:04:40 -04:00
|
|
|
config AUDIT_ARCH
|
|
|
|
bool
|
|
|
|
default y
|
|
|
|
|
2005-04-16 18:20:36 -04:00
|
|
|
choice
|
|
|
|
prompt "System type"
|
|
|
|
default IA64_GENERIC
|
|
|
|
|
|
|
|
config IA64_GENERIC
|
|
|
|
bool "generic"
|
2005-08-25 12:08:25 -04:00
|
|
|
select ACPI
|
2006-03-28 17:04:00 -05:00
|
|
|
select PCI
|
2005-04-16 18:20:36 -04:00
|
|
|
select NUMA
|
|
|
|
select ACPI_NUMA
|
|
|
|
help
|
|
|
|
This selects the system type of your hardware. A "generic" kernel
|
|
|
|
will run on any supported IA-64 system. However, if you configure
|
|
|
|
a kernel for your specific system, it will be faster and smaller.
|
|
|
|
|
|
|
|
generic For any supported IA-64 system
|
|
|
|
DIG-compliant For DIG ("Developer's Interface Guide") compliant systems
|
|
|
|
HP-zx1/sx1000 For HP systems
|
|
|
|
HP-zx1/sx1000+swiotlb For HP systems with (broken) DMA-constrained devices.
|
|
|
|
SGI-SN2 For SGI Altix systems
|
|
|
|
Ski-simulator For the HP simulator <http://www.hpl.hp.com/research/linux/ski/>
|
|
|
|
|
|
|
|
If you don't know what to do, choose "generic".
|
|
|
|
|
|
|
|
config IA64_DIG
|
|
|
|
bool "DIG-compliant"
|
|
|
|
|
|
|
|
config IA64_HP_ZX1
|
|
|
|
bool "HP-zx1/sx1000"
|
|
|
|
help
|
|
|
|
Build a kernel that runs on HP zx1 and sx1000 systems. This adds
|
|
|
|
support for the HP I/O MMU.
|
|
|
|
|
|
|
|
config IA64_HP_ZX1_SWIOTLB
|
|
|
|
bool "HP-zx1/sx1000 with software I/O TLB"
|
|
|
|
help
|
|
|
|
Build a kernel that runs on HP zx1 and sx1000 systems even when they
|
|
|
|
have broken PCI devices which cannot DMA to full 32 bits. Apart
|
|
|
|
from support for the HP I/O MMU, this includes support for the software
|
|
|
|
I/O TLB, which allows supporting the broken devices at the expense of
|
|
|
|
wasting some kernel memory (about 2MB by default).
|
|
|
|
|
|
|
|
config IA64_SGI_SN2
|
|
|
|
bool "SGI-SN2"
|
|
|
|
help
|
|
|
|
Selecting this option will optimize the kernel for use on sn2 based
|
|
|
|
systems, but the resulting kernel binary will not run on other
|
|
|
|
types of ia64 systems. If you have an SGI Altix system, it's safe
|
|
|
|
to select this option. If in doubt, select ia64 generic support
|
|
|
|
instead.
|
|
|
|
|
|
|
|
config IA64_HP_SIM
|
|
|
|
bool "Ski-simulator"
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
|
|
choice
|
|
|
|
prompt "Processor type"
|
|
|
|
default ITANIUM
|
|
|
|
|
|
|
|
config ITANIUM
|
|
|
|
bool "Itanium"
|
|
|
|
help
|
|
|
|
Select your IA-64 processor type. The default is Itanium.
|
|
|
|
This choice is safe for all IA-64 systems, but may not perform
|
|
|
|
optimally on systems with, say, Itanium 2 or newer processors.
|
|
|
|
|
|
|
|
config MCKINLEY
|
|
|
|
bool "Itanium 2"
|
|
|
|
help
|
|
|
|
Select this to configure for an Itanium 2 (McKinley) processor.
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
|
|
choice
|
|
|
|
prompt "Kernel page size"
|
|
|
|
default IA64_PAGE_SIZE_16KB
|
|
|
|
|
|
|
|
config IA64_PAGE_SIZE_4KB
|
|
|
|
bool "4KB"
|
|
|
|
help
|
|
|
|
This lets you select the page size of the kernel. For best IA-64
|
|
|
|
performance, a page size of 8KB or 16KB is recommended. For best
|
|
|
|
IA-32 compatibility, a page size of 4KB should be selected (the vast
|
|
|
|
majority of IA-32 binaries work perfectly fine with a larger page
|
|
|
|
size). For Itanium 2 or newer systems, a page size of 64KB can also
|
|
|
|
be selected.
|
|
|
|
|
|
|
|
4KB For best IA-32 compatibility
|
|
|
|
8KB For best IA-64 performance
|
|
|
|
16KB For best IA-64 performance
|
|
|
|
64KB Requires Itanium 2 or newer processor.
|
|
|
|
|
|
|
|
If you don't know what to do, choose 16KB.
|
|
|
|
|
|
|
|
config IA64_PAGE_SIZE_8KB
|
|
|
|
bool "8KB"
|
|
|
|
|
|
|
|
config IA64_PAGE_SIZE_16KB
|
|
|
|
bool "16KB"
|
|
|
|
|
|
|
|
config IA64_PAGE_SIZE_64KB
|
|
|
|
depends on !ITANIUM
|
|
|
|
bool "64KB"
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
2005-11-11 10:35:43 -05:00
|
|
|
choice
|
|
|
|
prompt "Page Table Levels"
|
|
|
|
default PGTABLE_3
|
|
|
|
|
|
|
|
config PGTABLE_3
|
|
|
|
bool "3 Levels"
|
|
|
|
|
|
|
|
config PGTABLE_4
|
|
|
|
depends on !IA64_PAGE_SIZE_64KB
|
|
|
|
bool "4 Levels"
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
2005-06-23 03:08:27 -04:00
|
|
|
source kernel/Kconfig.hz
|
|
|
|
|
2005-04-16 18:20:36 -04:00
|
|
|
config IA64_BRL_EMU
|
|
|
|
bool
|
|
|
|
depends on ITANIUM
|
|
|
|
default y
|
|
|
|
|
|
|
|
# align cache-sensitive data to 128 bytes
|
|
|
|
config IA64_L1_CACHE_SHIFT
|
|
|
|
int
|
|
|
|
default "7" if MCKINLEY
|
|
|
|
default "6" if ITANIUM
|
|
|
|
|
|
|
|
config IA64_CYCLONE
|
|
|
|
bool "Cyclone (EXA) Time Source support"
|
|
|
|
help
|
|
|
|
Say Y here to enable support for IBM EXA Cyclone time source.
|
|
|
|
If you're unsure, answer N.
|
|
|
|
|
|
|
|
config IOSAPIC
|
|
|
|
bool
|
|
|
|
depends on !IA64_HP_SIM
|
|
|
|
default y
|
|
|
|
|
2005-03-23 21:46:00 -05:00
|
|
|
config IA64_SGI_SN_XP
|
|
|
|
tristate "Support communication between SGI SSIs"
|
2005-11-01 11:21:51 -05:00
|
|
|
depends on IA64_GENERIC || IA64_SGI_SN2
|
2005-06-21 20:15:03 -04:00
|
|
|
select IA64_UNCACHED_ALLOCATOR
|
2005-03-23 21:46:00 -05:00
|
|
|
help
|
|
|
|
An SGI machine can be divided into multiple Single System
|
|
|
|
Images which act independently of each other and have
|
|
|
|
hardware based memory protection from the others. Enabling
|
|
|
|
this feature will allow for direct communication between SSIs
|
|
|
|
based on a network adapter and DMA messaging.
|
|
|
|
|
2005-04-16 18:20:36 -04:00
|
|
|
config FORCE_MAX_ZONEORDER
|
2005-10-04 15:13:37 -04:00
|
|
|
int "MAX_ORDER (11 - 17)" if !HUGETLB_PAGE
|
|
|
|
range 11 17 if !HUGETLB_PAGE
|
|
|
|
default "17" if HUGETLB_PAGE
|
|
|
|
default "11"
|
2005-04-16 18:20:36 -04:00
|
|
|
|
|
|
|
config SMP
|
|
|
|
bool "Symmetric multi-processing support"
|
|
|
|
help
|
|
|
|
This enables support for systems with more than one CPU. If you have
|
|
|
|
a system with only one CPU, say N. If you have a system with more
|
|
|
|
than one CPU, say Y.
|
|
|
|
|
|
|
|
If you say N here, the kernel will run on single and multiprocessor
|
|
|
|
systems, but will use only one CPU of a multiprocessor system. If
|
|
|
|
you say Y here, the kernel will run on many, but not all,
|
|
|
|
single processor systems. On a single processor system, the kernel
|
|
|
|
will run faster if you say N here.
|
|
|
|
|
|
|
|
See also the <file:Documentation/smp.txt> and the SMP-HOWTO
|
|
|
|
available at <http://www.tldp.org/docs.html#howto>.
|
|
|
|
|
|
|
|
If you don't know what to do here, say N.
|
|
|
|
|
|
|
|
config NR_CPUS
|
2005-09-14 11:33:40 -04:00
|
|
|
int "Maximum number of CPUs (2-1024)"
|
|
|
|
range 2 1024
|
2005-04-16 18:20:36 -04:00
|
|
|
depends on SMP
|
2006-08-22 22:43:27 -04:00
|
|
|
default "1024"
|
2005-04-16 18:20:36 -04:00
|
|
|
help
|
|
|
|
You should set this to the number of CPUs in your system, but
|
|
|
|
keep in mind that a kernel compiled for, e.g., 2 CPUs will boot but
|
|
|
|
only use 2 CPUs on a >2 CPU system. Setting this to a value larger
|
|
|
|
than 64 will cause the use of a CPU mask array, causing a small
|
|
|
|
performance hit.
|
|
|
|
|
|
|
|
config HOTPLUG_CPU
|
|
|
|
bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
|
|
|
|
depends on SMP && EXPERIMENTAL
|
|
|
|
select HOTPLUG
|
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
Say Y here to experiment with turning CPUs off and on. CPUs
|
|
|
|
can be controlled through /sys/devices/system/cpu/cpu#.
|
|
|
|
Say N if you want to disable CPU hotplug.
|
|
|
|
|
2006-06-29 05:24:27 -04:00
|
|
|
config ARCH_ENABLE_MEMORY_HOTPLUG
|
|
|
|
def_bool y
|
|
|
|
|
2005-04-05 21:05:00 -04:00
|
|
|
config SCHED_SMT
|
|
|
|
bool "SMT scheduler support"
|
|
|
|
depends on SMP
|
|
|
|
help
|
|
|
|
Improves the CPU scheduler's decision making when dealing with
|
|
|
|
Intel IA64 chips with MultiThreading at a cost of slightly increased
|
|
|
|
overhead in some places. If unsure say N here.
|
|
|
|
|
2005-11-11 17:32:40 -05:00
|
|
|
config PERMIT_BSP_REMOVE
|
|
|
|
bool "Support removal of Bootstrap Processor"
|
|
|
|
depends on HOTPLUG_CPU
|
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
Say Y here if your platform SAL will support removal of BSP with HOTPLUG_CPU
|
|
|
|
support.
|
|
|
|
|
|
|
|
config FORCE_CPEI_RETARGET
|
|
|
|
bool "Force assumption that CPEI can be re-targetted"
|
|
|
|
depends on PERMIT_BSP_REMOVE
|
|
|
|
default n
|
|
|
|
---help---
|
|
|
|
Say Y if you need to force the assumption that CPEI can be re-targetted to
|
|
|
|
any cpu in the system. This hint is available via ACPI 3.0 specifications.
|
|
|
|
Tiger4 systems are capable of re-directing CPEI to any CPU other than BSP.
|
|
|
|
This option it useful to enable this feature on older BIOS's as well.
|
|
|
|
You can also enable this by using boot command line option force_cpei=1.
|
|
|
|
|
2005-04-16 18:20:36 -04:00
|
|
|
config PREEMPT
|
|
|
|
bool "Preemptible Kernel"
|
|
|
|
help
|
|
|
|
This option reduces the latency of the kernel when reacting to
|
|
|
|
real-time or interactive events by allowing a low priority process to
|
|
|
|
be preempted even if it is in kernel mode executing a system call.
|
|
|
|
This allows applications to run more reliably even when the system is
|
|
|
|
under load.
|
|
|
|
|
|
|
|
Say Y here if you are building a kernel for a desktop, embedded
|
|
|
|
or real-time system. Say N if you are unsure.
|
|
|
|
|
2005-06-23 03:07:43 -04:00
|
|
|
source "mm/Kconfig"
|
|
|
|
|
2005-10-04 15:13:37 -04:00
|
|
|
config ARCH_SELECT_MEMORY_MODEL
|
|
|
|
def_bool y
|
|
|
|
|
|
|
|
config ARCH_DISCONTIGMEM_ENABLE
|
|
|
|
def_bool y
|
|
|
|
help
|
|
|
|
Say Y to support efficient handling of discontiguous physical memory,
|
|
|
|
for architectures which are either NUMA (Non-Uniform Memory Access)
|
|
|
|
or have huge holes in the physical address space for other reasons.
|
|
|
|
See <file:Documentation/vm/numa> for more.
|
|
|
|
|
|
|
|
config ARCH_FLATMEM_ENABLE
|
|
|
|
def_bool y
|
|
|
|
|
|
|
|
config ARCH_SPARSEMEM_ENABLE
|
|
|
|
def_bool y
|
|
|
|
depends on ARCH_DISCONTIGMEM_ENABLE
|
|
|
|
|
|
|
|
config ARCH_DISCONTIGMEM_DEFAULT
|
|
|
|
def_bool y if (IA64_SGI_SN2 || IA64_GENERIC || IA64_HP_ZX1 || IA64_HP_ZX1_SWIOTLB)
|
|
|
|
depends on ARCH_DISCONTIGMEM_ENABLE
|
|
|
|
|
|
|
|
config NUMA
|
|
|
|
bool "NUMA support"
|
|
|
|
depends on !IA64_HP_SIM && !FLATMEM
|
|
|
|
default y if IA64_SGI_SN2
|
2006-11-08 20:44:50 -05:00
|
|
|
select ACPI_NUMA if ACPI
|
2005-10-04 15:13:37 -04:00
|
|
|
help
|
|
|
|
Say Y to compile the kernel to support NUMA (Non-Uniform Memory
|
|
|
|
Access). This option is for configuring high-end multiprocessor
|
|
|
|
server systems. If in doubt, say N.
|
|
|
|
|
2006-04-11 01:53:53 -04:00
|
|
|
config NODES_SHIFT
|
|
|
|
int "Max num nodes shift(3-10)"
|
|
|
|
range 3 10
|
2006-08-22 22:43:27 -04:00
|
|
|
default "10"
|
2006-04-11 01:53:53 -04:00
|
|
|
depends on NEED_MULTIPLE_NODES
|
|
|
|
help
|
|
|
|
This option specifies the maximum number of nodes in your SSI system.
|
|
|
|
MAX_NUMNODES will be 2^(This value).
|
|
|
|
If in doubt, use the default.
|
|
|
|
|
2006-09-27 04:49:54 -04:00
|
|
|
config ARCH_POPULATES_NODE_MAP
|
|
|
|
def_bool y
|
|
|
|
|
2005-10-04 15:13:37 -04:00
|
|
|
# VIRTUAL_MEM_MAP and FLAT_NODE_MEM_MAP are functionally equivalent.
|
|
|
|
# VIRTUAL_MEM_MAP has been retained for historical reasons.
|
|
|
|
config VIRTUAL_MEM_MAP
|
|
|
|
bool "Virtual mem map"
|
|
|
|
depends on !SPARSEMEM
|
|
|
|
default y if !IA64_HP_SIM
|
|
|
|
help
|
|
|
|
Say Y to compile the kernel with support for a virtual mem map.
|
|
|
|
This code also only takes effect if a memory hole of greater than
|
|
|
|
1 Gb is found during boot. You must turn this option on if you
|
|
|
|
require the DISCONTIGMEM option for your machine. If you are
|
|
|
|
unsure, say Y.
|
|
|
|
|
|
|
|
config HOLES_IN_ZONE
|
|
|
|
bool
|
|
|
|
default y if VIRTUAL_MEM_MAP
|
|
|
|
|
|
|
|
config HAVE_ARCH_EARLY_PFN_TO_NID
|
|
|
|
def_bool y
|
|
|
|
depends on NEED_MULTIPLE_NODES
|
|
|
|
|
2006-06-27 05:53:33 -04:00
|
|
|
config HAVE_ARCH_NODEDATA_EXTENSION
|
|
|
|
def_bool y
|
|
|
|
depends on NUMA
|
|
|
|
|
2005-04-16 18:20:36 -04:00
|
|
|
config IA32_SUPPORT
|
|
|
|
bool "Support for Linux/x86 binaries"
|
|
|
|
help
|
|
|
|
IA-64 processors can execute IA-32 (X86) instructions. By
|
|
|
|
saying Y here, the kernel will include IA-32 system call
|
|
|
|
emulation support which makes it possible to transparently
|
|
|
|
run IA-32 Linux binaries on an IA-64 Linux system.
|
|
|
|
If in doubt, say Y.
|
|
|
|
|
|
|
|
config COMPAT
|
|
|
|
bool
|
|
|
|
depends on IA32_SUPPORT
|
|
|
|
default y
|
|
|
|
|
|
|
|
config IA64_MCA_RECOVERY
|
|
|
|
tristate "MCA recovery from errors other than TLB."
|
|
|
|
|
|
|
|
config PERFMON
|
|
|
|
bool "Performance monitor support"
|
|
|
|
help
|
|
|
|
Selects whether support for the IA-64 performance monitor hardware
|
|
|
|
is included in the kernel. This makes some kernel data-structures a
|
|
|
|
little bigger and slows down execution a bit, but it is generally
|
|
|
|
a good idea to turn this on. If you're unsure, say Y.
|
|
|
|
|
|
|
|
config IA64_PALINFO
|
|
|
|
tristate "/proc/pal support"
|
|
|
|
help
|
|
|
|
If you say Y here, you are able to get PAL (Processor Abstraction
|
|
|
|
Layer) information in /proc/pal. This contains useful information
|
|
|
|
about the processors in your systems, such as cache and TLB sizes
|
|
|
|
and the PAL firmware version in use.
|
|
|
|
|
|
|
|
To use this option, you have to ensure that the "/proc file system
|
|
|
|
support" (CONFIG_PROC_FS) is enabled, too.
|
|
|
|
|
2006-01-19 04:54:00 -05:00
|
|
|
config SGI_SN
|
|
|
|
def_bool y if (IA64_SGI_SN2 || IA64_GENERIC)
|
|
|
|
|
[IA64] esi-support
Add support for making ESI calls [1]. ESI stands for "Extensible SAL
specification" and is basically a way for invoking firmware
subroutines which are identified by a GUID. I don't know whether ESI
is used by vendors other than HP (if you do, please let me know) but
as firmware "backdoors" go, this seems one of the cleaner methods, so
it seems reasonable to support it, even though I'm not aware of any
publicly documented ESI calls. I'd have liked to make the ESI module
completely stand-alone, but unfortunately that is not easily (or not
at all) possible because in order to make ESI calls in physical mode,
a small stub similar to the EFI stub is needed in the kernel proper.
I did try to create a stub that would work in user-level, but it
quickly got ugly beyond recognition (e.g., the stub had to make
assumptions about how the module-loader generated call-stubs work) and
I didn't even get it to work (that's probably fixable, but I didn't
bother because I concluded it was too ugly anyhow). While it's not
terribly elegant to have kernel code which isn't actively used in the
kernel proper, I think it might be worth making an exception here for
two reasons: the code is trivially small (all that's really needed is
esi_stub.S) and by including it in the normal kernel distro, it might
encourage other OEMs to also use ESI, which I think would be far
better than each inventing their own firmware "backdoor".
The code was originally written by Alex. I just massaged and packaged
it a bit (and perhaps messed up some things along the way...).
Changes since first version of patch that was posted to mailing list:
* Export ia64_esi_call and ia64_esi_call_phys() as GPL symbols.
* Disallow building esi.c as a module for now. Building as a module
would currently lead to an unresolved reference to "sal_lock" on SMP kernels
because that symbol doesn't get exported.
* Export esi_call_phys() only if ESI is enabled.
* Remove internal stuff from esi.h and add a "proc_type" argument to
ia64_esi_call() such that serialization-requirements can be expressed (ESI
follows SAL here, where procedure calls may have to be serialized, are
MP-safe, or MP-safe andr reentrant).
[1] h21007.www2.hp.com/dspp/tech/tech_TechDocumentDetailPage_IDX/1,1701,919,00.html
Signed-off-by: David Mosberger <David.Mosberger@acm.org>
Signed-off-by: Alex Williamson <alex.williamson@hp.com>
Signed-off-by: Tony Luck <tony.luck@intel.com>
2006-06-21 14:19:22 -04:00
|
|
|
config IA64_ESI
|
|
|
|
bool "ESI (Extensible SAL Interface) support"
|
|
|
|
help
|
|
|
|
If you say Y here, support is built into the kernel to
|
|
|
|
make ESI calls. ESI calls are used to support vendor-specific
|
|
|
|
firmware extensions, such as the ability to inject memory-errors
|
|
|
|
for test-purposes. If you're unsure, say N.
|
|
|
|
|
2006-04-20 16:38:16 -04:00
|
|
|
source "drivers/sn/Kconfig"
|
|
|
|
|
2005-04-16 18:20:36 -04:00
|
|
|
source "drivers/firmware/Kconfig"
|
|
|
|
|
|
|
|
source "fs/Kconfig.binfmt"
|
|
|
|
|
|
|
|
endmenu
|
|
|
|
|
|
|
|
menu "Power management and ACPI"
|
|
|
|
|
2005-08-25 12:08:25 -04:00
|
|
|
source "kernel/power/Kconfig"
|
2005-04-16 18:20:36 -04:00
|
|
|
|
|
|
|
source "drivers/acpi/Kconfig"
|
|
|
|
|
2005-07-29 19:15:00 -04:00
|
|
|
if PM
|
|
|
|
|
|
|
|
source "arch/ia64/kernel/cpufreq/Kconfig"
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
2005-04-16 18:20:36 -04:00
|
|
|
endmenu
|
|
|
|
|
|
|
|
if !IA64_HP_SIM
|
|
|
|
|
|
|
|
menu "Bus options (PCI, PCMCIA)"
|
|
|
|
|
|
|
|
config PCI
|
|
|
|
bool "PCI support"
|
|
|
|
help
|
2005-08-09 16:38:00 -04:00
|
|
|
Real IA-64 machines all have PCI/PCI-X/PCI Express busses. Say Y
|
|
|
|
here unless you are using a simulator without PCI support.
|
2005-04-16 18:20:36 -04:00
|
|
|
|
|
|
|
config PCI_DOMAINS
|
|
|
|
bool
|
|
|
|
default PCI
|
|
|
|
|
2006-04-27 22:50:43 -04:00
|
|
|
source "drivers/pci/pcie/Kconfig"
|
|
|
|
|
2005-04-16 18:20:36 -04:00
|
|
|
source "drivers/pci/Kconfig"
|
|
|
|
|
|
|
|
source "drivers/pci/hotplug/Kconfig"
|
|
|
|
|
|
|
|
source "drivers/pcmcia/Kconfig"
|
|
|
|
|
|
|
|
endmenu
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
2005-07-12 00:03:49 -04:00
|
|
|
source "net/Kconfig"
|
|
|
|
|
2005-04-16 18:20:36 -04:00
|
|
|
source "drivers/Kconfig"
|
|
|
|
|
2006-11-10 15:27:49 -05:00
|
|
|
config MSPEC
|
|
|
|
tristate "Memory special operations driver"
|
|
|
|
depends on IA64
|
|
|
|
select IA64_UNCACHED_ALLOCATOR
|
|
|
|
help
|
|
|
|
If you have an ia64 and you want to enable memory special
|
|
|
|
operations support (formerly known as fetchop), say Y here,
|
|
|
|
otherwise say N.
|
|
|
|
|
2005-04-16 18:20:36 -04:00
|
|
|
source "fs/Kconfig"
|
|
|
|
|
|
|
|
source "lib/Kconfig"
|
|
|
|
|
|
|
|
#
|
|
|
|
# Use the generic interrupt handling code in kernel/irq/:
|
|
|
|
#
|
|
|
|
config GENERIC_HARDIRQS
|
|
|
|
bool
|
|
|
|
default y
|
|
|
|
|
|
|
|
config GENERIC_IRQ_PROBE
|
|
|
|
bool
|
|
|
|
default y
|
|
|
|
|
[PATCH] x86/x86_64: deferred handling of writes to /proc/irqxx/smp_affinity
When handling writes to /proc/irq, current code is re-programming rte
entries directly. This is not recommended and could potentially cause
chipset's to lockup, or cause missing interrupts.
CONFIG_IRQ_BALANCE does this correctly, where it re-programs only when the
interrupt is pending. The same needs to be done for /proc/irq handling as well.
Otherwise user space irq balancers are really not doing the right thing.
- Changed pending_irq_balance_cpumask to pending_irq_migrate_cpumask for
lack of a generic name.
- added move_irq out of IRQ_BALANCE, and added this same to X86_64
- Added new proc handler for write, so we can do deferred write at irq
handling time.
- Display of /proc/irq/XX/smp_affinity used to display CPU_MASKALL, instead
it now shows only active cpu masks, or exactly what was set.
- Provided a common move_irq implementation, instead of duplicating
when using generic irq framework.
Tested on i386/x86_64 and ia64 with CONFIG_PCI_MSI turned on and off.
Tested UP builds as well.
MSI testing: tbd: I have cards, need to look for a x-over cable, although I
did test an earlier version of this patch. Will test in a couple days.
Signed-off-by: Ashok Raj <ashok.raj@intel.com>
Acked-by: Zwane Mwaikambo <zwane@holomorphy.com>
Grudgingly-acked-by: Andi Kleen <ak@muc.de>
Signed-off-by: Coywolf Qi Hunt <coywolf@lovecn.org>
Signed-off-by: Ashok Raj <ashok.raj@intel.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-09-06 18:16:15 -04:00
|
|
|
config GENERIC_PENDING_IRQ
|
|
|
|
bool
|
|
|
|
depends on GENERIC_HARDIRQS && SMP
|
|
|
|
default y
|
|
|
|
|
2006-06-29 05:24:43 -04:00
|
|
|
config IRQ_PER_CPU
|
|
|
|
bool
|
|
|
|
default y
|
|
|
|
|
2005-04-16 18:20:36 -04:00
|
|
|
source "arch/ia64/hp/sim/Kconfig"
|
|
|
|
|
2005-11-07 03:59:14 -05:00
|
|
|
menu "Instrumentation Support"
|
|
|
|
depends on EXPERIMENTAL
|
|
|
|
|
2005-04-16 18:20:36 -04:00
|
|
|
source "arch/ia64/oprofile/Kconfig"
|
|
|
|
|
2005-11-07 03:59:14 -05:00
|
|
|
config KPROBES
|
|
|
|
bool "Kprobes (EXPERIMENTAL)"
|
2006-10-02 05:17:30 -04:00
|
|
|
depends on KALLSYMS && EXPERIMENTAL && MODULES
|
2005-11-07 03:59:14 -05:00
|
|
|
help
|
|
|
|
Kprobes allows you to trap at almost any kernel address and
|
|
|
|
execute a callback function. register_kprobe() establishes
|
|
|
|
a probepoint and specifies the callback. Kprobes is useful
|
|
|
|
for kernel debugging, non-intrusive instrumentation and testing.
|
|
|
|
If in doubt, say "N".
|
|
|
|
endmenu
|
|
|
|
|
2005-04-16 18:20:36 -04:00
|
|
|
source "arch/ia64/Kconfig.debug"
|
|
|
|
|
|
|
|
source "security/Kconfig"
|
|
|
|
|
|
|
|
source "crypto/Kconfig"
|