3 select ARCH_HAS_DEBUG_STRICT_USER_COPY_CHECKS
4 select ARCH_MIGHT_HAVE_PC_PARPORT
7 select HAVE_FUNCTION_TRACER if 64BIT
8 select HAVE_FUNCTION_GRAPH_TRACER if 64BIT
9 select ARCH_WANT_FRAME_POINTERS
11 select RTC_DRV_GENERIC
12 select INIT_ALL_POSSIBLE
14 select HAVE_PERF_EVENTS
15 select GENERIC_ATOMIC64 if !64BIT
16 select ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE
18 select GENERIC_IRQ_PROBE
19 select GENERIC_PCI_IOMAP
20 select ARCH_HAVE_NMI_SAFE_CMPXCHG
21 select GENERIC_SMP_IDLE_THREAD
22 select GENERIC_STRNCPY_FROM_USER
23 select SYSCTL_ARCH_UNALIGN_ALLOW
24 select SYSCTL_EXCEPTION_TRACE
25 select HAVE_MOD_ARCH_SPECIFIC
27 select MODULES_USE_ELF_RELA
28 select CLONE_BACKWARDS
29 select TTY # Needed for pdc_cons.c
30 select HAVE_DEBUG_STACKOVERFLOW
31 select HAVE_ARCH_AUDITSYSCALL
34 The PA-RISC microprocessor is designed by Hewlett-Packard and used
35 in many of their workstations & servers (HP9000 700 and 800 series,
36 and later HP3000 series). The PA-RISC Linux project home page is
37 at <http://www.parisc-linux.org/>.
45 config GENERIC_LOCKBREAK
48 depends on SMP && PREEMPT
50 config RWSEM_GENERIC_SPINLOCK
53 config RWSEM_XCHGADD_ALGORITHM
56 config ARCH_HAS_ILOG2_U32
60 config ARCH_HAS_ILOG2_U64
69 config GENERIC_HWEIGHT
73 config GENERIC_CALIBRATE_DELAY
82 config HAVE_LATENCYTOP_SUPPORT
85 # unless you want to implement ACPI on PA-RISC ... ;-)
89 config STACKTRACE_SUPPORT
92 config NEED_DMA_MAP_STATE
95 config NEED_SG_DMA_LENGTH
101 config ARCH_MAY_HAVE_PC_FDC
106 config PGTABLE_LEVELS
108 default 3 if 64BIT && PARISC_PAGE_SIZE_4KB
111 config SYS_SUPPORTS_HUGETLBFS
114 source "init/Kconfig"
116 source "kernel/Kconfig.freezer"
119 menu "Processor type and features"
122 prompt "Processor type"
128 This is the processor type of your CPU. This information is
129 used for optimizing purposes. In order to compile a kernel
130 that can run on all 32-bit PA CPUs (albeit not optimally fast),
131 you can specify "PA7000" here.
133 Specifying "PA8000" here will allow you to select a 64-bit kernel
134 which is required on some machines.
139 Select this option for the PCX-L processor, as used in the
140 712, 715/64, 715/80, 715/100, 715/100XC, 725/100, 743, 748,
141 D200, D210, D300, D310 and E-class
146 Select this option for the PCX-T' processor, as used in the
147 C100, C110, J100, J110, J210XC, D250, D260, D350, D360,
148 K100, K200, K210, K220, K400, K410 and K420
153 Select this option for the PCX-L2 processor, as used in the
154 744, A180, B132L, B160L, B180L, C132L, C160L, C180L,
155 D220, D230, D320 and D330.
160 Select this option for PCX-U to PCX-W2 processors.
164 # Define implied options from the CPU selection here
172 depends on PA7000 || PA7100LC || PA7200 || PA7300LC
176 depends on PA8X00 || PA7200
179 bool "Enable the -mlong-calls compiler option for big kernels"
180 def_bool y if (!MODULES)
183 If you configure the kernel to include many drivers built-in instead
184 as modules, the kernel executable may become too big, so that the
185 linker will not be able to resolve some long branches and fails to link
186 your vmlinux kernel. In that case enabling this option will help you
187 to overcome this limit by using the -mlong-calls compiler option.
189 Usually you want to say N here, unless you e.g. want to build
190 a kernel which includes all necessary drivers built-in and which can
191 be used for TFTP booting without the need to have an initrd ramdisk.
193 Enabling this option will probably slow down your kernel.
199 Enable this if you want to support 64bit kernel on PA-RISC platform.
201 At the moment, only people willing to use more than 2GB of RAM,
202 or having a 64bit-only capable PA-RISC machine should say Y here.
204 Since there is no 64bit userland on PA-RISC, there is no point to
205 enable this option otherwise. The 64bit kernel is significantly bigger
206 and slower than the 32bit one.
209 prompt "Kernel page size"
210 default PARISC_PAGE_SIZE_4KB
212 config PARISC_PAGE_SIZE_4KB
215 This lets you select the page size of the kernel. For best
216 performance, a page size of 16KB is recommended. For best
217 compatibility with 32bit applications, a page size of 4KB should be
218 selected (the vast majority of 32bit binaries work perfectly fine
219 with a larger page size).
221 4KB For best 32bit compatibility
222 16KB For best performance
223 64KB For best performance, might give more overhead.
225 If you don't know what to do, choose 4KB.
227 config PARISC_PAGE_SIZE_16KB
231 config PARISC_PAGE_SIZE_64KB
238 bool "Symmetric multi-processing support"
240 This enables support for systems with more than one CPU. If you have
241 a system with only one CPU, say N. If you have a system with more
244 If you say N here, the kernel will run on uni- and multiprocessor
245 machines, but will use only one CPU of a multiprocessor machine. If
246 you say Y here, the kernel will run on many, but not all,
247 uniprocessor machines. On a uniprocessor machine, the kernel
248 will run faster if you say N here.
250 See also <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO
251 available at <http://www.tldp.org/docs.html#howto>.
253 If you don't know what to do here, say N.
256 bool "Use separate kernel stacks when processing interrupts"
259 If you say Y here the kernel will use separate kernel stacks
260 for handling hard and soft interrupts. This can help avoid
261 overflowing the process kernel stacks.
267 config ARCH_SELECT_MEMORY_MODEL
271 config ARCH_DISCONTIGMEM_ENABLE
275 config ARCH_FLATMEM_ENABLE
278 config ARCH_DISCONTIGMEM_DEFAULT
280 depends on ARCH_DISCONTIGMEM_ENABLE
285 depends on NEED_MULTIPLE_NODES
287 source "kernel/Kconfig.preempt"
288 source "kernel/Kconfig.hz"
295 config SYSVIPC_COMPAT
297 depends on COMPAT && SYSVIPC
303 int "Maximum number of CPUs (2-32)"
311 source "drivers/parisc/Kconfig"
314 menu "Executable file formats"
316 source "fs/Kconfig.binfmt"
322 source "drivers/Kconfig"
326 source "arch/parisc/Kconfig.debug"
330 prompt "Enable seccomp to safely compute untrusted bytecode"
332 This kernel feature is useful for number crunching applications
333 that may need to compute untrusted bytecode during their
334 execution. By using pipes or other transports made available to
335 the process as file descriptors supporting the read/write
336 syscalls, it's possible to isolate those applications in
337 their own address space using seccomp. Once seccomp is
338 enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
339 and the task is only allowed to execute a few safe syscalls
340 defined by each seccomp mode.
342 If unsure, say Y. Only embedded should say N here.
344 source "security/Kconfig"
346 source "crypto/Kconfig"