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 source "init/Kconfig"
108 source "kernel/Kconfig.freezer"
111 menu "Processor type and features"
114 prompt "Processor type"
120 This is the processor type of your CPU. This information is
121 used for optimizing purposes. In order to compile a kernel
122 that can run on all 32-bit PA CPUs (albeit not optimally fast),
123 you can specify "PA7000" here.
125 Specifying "PA8000" here will allow you to select a 64-bit kernel
126 which is required on some machines.
131 Select this option for the PCX-L processor, as used in the
132 712, 715/64, 715/80, 715/100, 715/100XC, 725/100, 743, 748,
133 D200, D210, D300, D310 and E-class
138 Select this option for the PCX-T' processor, as used in the
139 C100, C110, J100, J110, J210XC, D250, D260, D350, D360,
140 K100, K200, K210, K220, K400, K410 and K420
145 Select this option for the PCX-L2 processor, as used in the
146 744, A180, B132L, B160L, B180L, C132L, C160L, C180L,
147 D220, D230, D320 and D330.
152 Select this option for PCX-U to PCX-W2 processors.
156 # Define implied options from the CPU selection here
164 depends on PA7000 || PA7100LC || PA7200 || PA7300LC
168 depends on PA8X00 || PA7200
171 bool "Enable the -mlong-calls compiler option for big kernels"
172 def_bool y if (!MODULES)
175 If you configure the kernel to include many drivers built-in instead
176 as modules, the kernel executable may become too big, so that the
177 linker will not be able to resolve some long branches and fails to link
178 your vmlinux kernel. In that case enabling this option will help you
179 to overcome this limit by using the -mlong-calls compiler option.
181 Usually you want to say N here, unless you e.g. want to build
182 a kernel which includes all necessary drivers built-in and which can
183 be used for TFTP booting without the need to have an initrd ramdisk.
185 Enabling this option will probably slow down your kernel.
191 Enable this if you want to support 64bit kernel on PA-RISC platform.
193 At the moment, only people willing to use more than 2GB of RAM,
194 or having a 64bit-only capable PA-RISC machine should say Y here.
196 Since there is no 64bit userland on PA-RISC, there is no point to
197 enable this option otherwise. The 64bit kernel is significantly bigger
198 and slower than the 32bit one.
201 prompt "Kernel page size"
202 default PARISC_PAGE_SIZE_4KB
204 config PARISC_PAGE_SIZE_4KB
207 This lets you select the page size of the kernel. For best
208 performance, a page size of 16KB is recommended. For best
209 compatibility with 32bit applications, a page size of 4KB should be
210 selected (the vast majority of 32bit binaries work perfectly fine
211 with a larger page size).
213 4KB For best 32bit compatibility
214 16KB For best performance
215 64KB For best performance, might give more overhead.
217 If you don't know what to do, choose 4KB.
219 config PARISC_PAGE_SIZE_16KB
223 config PARISC_PAGE_SIZE_64KB
230 bool "Symmetric multi-processing support"
232 This enables support for systems with more than one CPU. If you have
233 a system with only one CPU, say N. If you have a system with more
236 If you say N here, the kernel will run on uni- and multiprocessor
237 machines, but will use only one CPU of a multiprocessor machine. If
238 you say Y here, the kernel will run on many, but not all,
239 uniprocessor machines. On a uniprocessor machine, the kernel
240 will run faster if you say N here.
242 See also <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO
243 available at <http://www.tldp.org/docs.html#howto>.
245 If you don't know what to do here, say N.
248 bool "Use separate kernel stacks when processing interrupts"
251 If you say Y here the kernel will use separate kernel stacks
252 for handling hard and soft interrupts. This can help avoid
253 overflowing the process kernel stacks.
259 config ARCH_SELECT_MEMORY_MODEL
263 config ARCH_DISCONTIGMEM_ENABLE
267 config ARCH_FLATMEM_ENABLE
270 config ARCH_DISCONTIGMEM_DEFAULT
272 depends on ARCH_DISCONTIGMEM_ENABLE
277 depends on NEED_MULTIPLE_NODES
279 source "kernel/Kconfig.preempt"
280 source "kernel/Kconfig.hz"
287 config SYSVIPC_COMPAT
289 depends on COMPAT && SYSVIPC
295 int "Maximum number of CPUs (2-32)"
303 source "drivers/parisc/Kconfig"
306 menu "Executable file formats"
308 source "fs/Kconfig.binfmt"
314 source "drivers/Kconfig"
318 source "arch/parisc/Kconfig.debug"
322 prompt "Enable seccomp to safely compute untrusted bytecode"
324 This kernel feature is useful for number crunching applications
325 that may need to compute untrusted bytecode during their
326 execution. By using pipes or other transports made available to
327 the process as file descriptors supporting the read/write
328 syscalls, it's possible to isolate those applications in
329 their own address space using seccomp. Once seccomp is
330 enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
331 and the task is only allowed to execute a few safe syscalls
332 defined by each seccomp mode.
334 If unsure, say Y. Only embedded should say N here.
336 source "security/Kconfig"
338 source "crypto/Kconfig"