Lines Matching +full:multi +full:- +full:system

1 # SPDX-License-Identifier: GPL-2.0
61 select HAVE_DYNAMIC_FTRACE if $(cc-option,-fpatchable-function-entry=1,1)
70 The PA-RISC microprocessor is designed by Hewlett-Packard and used
72 and later HP3000 series). The PA-RISC Linux project home page is
86 default "arch/parisc/configs/generic-32bit_defconfig" if !64BIT
87 default "arch/parisc/configs/generic-64bit_defconfig" if 64BIT
120 # unless you want to implement ACPI on PA-RISC ... ;-)
151 that can run on all 32-bit PA CPUs (albeit not optimally fast),
154 Specifying "PA8000" here will allow you to select a 64-bit kernel
160 Select this option for the PCX-L processor, as used in the
162 D200, D210, D300, D310 and E-class
167 Select this option for the PCX-T' processor, as used in the
174 Select this option for the PCX-L2 processor, as used in the
181 Select this option for PCX-U to PCX-W2 processors.
206 bool "Enable the -mlong-calls compiler option for big kernels" if !PARISC_HUGE_KERNEL
209 If you configure the kernel to include many drivers built-in instead
213 to overcome this limit by using the -mlong-calls compiler option.
216 a kernel which includes all necessary drivers built-in and which can
222 bool "64-bit kernel"
225 Enable this if you want to support 64bit kernel on PA-RISC platform.
228 or having a 64bit-only capable PA-RISC machine should say Y here.
230 Since there is no 64bit userland on PA-RISC, there is no point to
264 bool "Build kernel as self-extracting executable"
268 self-extracting executable.
276 bool "Symmetric multi-processing support"
279 a system with only one CPU, say N. If you have a system with more
282 If you say N here, the kernel will run on uni- and multiprocessor
286 See also <file:Documentation/admin-guide/lockup-watchdogs.rst> and the SMP-HOWTO
299 bool "Multi-core scheduler support"
302 Multi-core scheduler support improves the CPU scheduler's decision
303 making when dealing with multi-core CPU chips at a cost of slightly
357 int "Maximum number of CPUs (2-32)"
363 bool "Kexec system call"
366 kexec is a system call that implements the ability to shutdown your
368 but it is independent of the system firmware. And like a reboot
376 bool "kexec file based system call"
380 This enables the kexec_file_load() System call. This is
381 file based and takes file descriptors as system call argument
383 accepted by previous system call.