Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit ea6e942b authored by Atsushi Nemoto's avatar Atsushi Nemoto Committed by Ralf Baechle
Browse files

[MIPS] Kconfig: Move some entries to appropriate menu 



Currently KEXEC is in "Machine selection", SECCOMP, PM, APM are in
"Executable file formats" menu.  Move KEXEC and SECCOMP to "Kernel
type" and PM, APM to new "Power management options" menu.  Also
replace "config PM" with kernel/power/Kconfig.

Signed-off-by: default avatarAtsushi Nemoto <anemo@mba.ocn.ne.jp>
Signed-off-by: default avatarRalf Baechle <ralf@linux-mips.org>
parent 9a0ad9e9

arch/mips/Kconfig

+34 −34
Original line number Original line Diff line number Diff line
@@ -790,23 +790,6 @@ config TOSHIBA_RBTX4938 




endchoice

endchoice





config KEXEC

 	bool "Kexec system call (EXPERIMENTAL)"

 	depends on EXPERIMENTAL

 	help

 	  kexec is a system call that implements the ability to shutdown your

 	  current kernel, and to start another kernel.  It is like a reboot

 	  but it is indepedent of the system firmware.   And like a reboot

 	  you can start any kernel with it, not just Linux.



 	  The name comes from the similiarity to the exec system call.



 	  It is an ongoing process to be certain the hardware in a machine

 	  is properly shutdown, so do not be surprised if this code does not

 	  initially work for you.  It may help to enable device hotplugging

 	  support.  As of this writing the exact hardware interface is

 	  strongly in flux, so no good recommendation can be made.



source "arch/mips/ddb5xxx/Kconfig"

source "arch/mips/ddb5xxx/Kconfig"

source "arch/mips/gt64120/ev64120/Kconfig"

source "arch/mips/gt64120/ev64120/Kconfig"

source "arch/mips/jazz/Kconfig"

source "arch/mips/jazz/Kconfig"
@@ -1859,6 +1842,40 @@ config MIPS_INSANE_LARGE 
	  This will result in additional memory usage, so it is not

	  This will result in additional memory usage, so it is not

	  recommended for normal users.

	  recommended for normal users.





config KEXEC

	bool "Kexec system call (EXPERIMENTAL)"

	depends on EXPERIMENTAL

	help

	  kexec is a system call that implements the ability to shutdown your

	  current kernel, and to start another kernel.  It is like a reboot

	  but it is indepedent of the system firmware.   And like a reboot

	  you can start any kernel with it, not just Linux.



	  The name comes from the similiarity to the exec system call.



	  It is an ongoing process to be certain the hardware in a machine

	  is properly shutdown, so do not be surprised if this code does not

	  initially work for you.  It may help to enable device hotplugging

	  support.  As of this writing the exact hardware interface is

	  strongly in flux, so no good recommendation can be made.



config SECCOMP

	bool "Enable seccomp to safely compute untrusted bytecode"

	depends on PROC_FS && BROKEN

	default y

	help

	  This kernel feature is useful for number crunching applications

	  that may need to compute untrusted bytecode during their

	  execution. By using pipes or other transports made available to

	  the process as file descriptors supporting the read/write

	  syscalls, it's possible to isolate those applications in

	  their own address space using seccomp. Once seccomp is

	  enabled via /proc/<pid>/seccomp, it cannot be disabled

	  and the task is only allowed to execute a few safe syscalls

	  defined by each seccomp mode.



	  If unsure, say Y. Only embedded should say N here.



endmenu

endmenu





config RWSEM_GENERIC_SPINLOCK

config RWSEM_GENERIC_SPINLOCK
@@ -2025,23 +2042,6 @@ config BINFMT_ELF32 
	bool

	bool

	default y if MIPS32_O32 || MIPS32_N32

	default y if MIPS32_O32 || MIPS32_N32





config SECCOMP

	bool "Enable seccomp to safely compute untrusted bytecode"

	depends on PROC_FS && BROKEN

	default y

	help

	  This kernel feature is useful for number crunching applications

	  that may need to compute untrusted bytecode during their

	  execution. By using pipes or other transports made available to

	  the process as file descriptors supporting the read/write

	  syscalls, it's possible to isolate those applications in

	  their own address space using seccomp. Once seccomp is

	  enabled via /proc/<pid>/seccomp, it cannot be disabled

	  and the task is only allowed to execute a few safe syscalls

	  defined by each seccomp mode.



	  If unsure, say Y. Only embedded should say N here.



config PM

config PM

	bool "Power Management support (EXPERIMENTAL)"

	bool "Power Management support (EXPERIMENTAL)"

	depends on EXPERIMENTAL && SOC_AU1X00

	depends on EXPERIMENTAL && SOC_AU1X00