linux-kernel - [PATCH] [1/3] x86: Improve CONFIG_KEXEC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Sun,  6 Dec 2009 15:13:09 +0100 (CET)
From:	Andi Kleen <andi@...stfloor.org>
To:	ying.huang@...el.com, x86@...nel.org, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org
Subject: [PATCH] [1/3] x86: Improve CONFIG_KEXEC_JUMP description


I've been puzzling what CONFIG_KEXEC_JUMP was good for.

The Kconfig help was not very helpful in explaining why one
want to set this option. This patch improves 
it a bit, based on the original commit log. It's still
not fully clear, but then I couldn't find a concrete application
anywhere.

Cc: ying.huang@...el.com
Signed-off-by: Andi Kleen <ak@...ux.intel.com>

---
 arch/x86/Kconfig |    6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

Index: linux-2.6.32-ak/arch/x86/Kconfig
===================================================================
--- linux-2.6.32-ak.orig/arch/x86/Kconfig
+++ linux-2.6.32-ak/arch/x86/Kconfig
@@ -1496,8 +1496,10 @@ config KEXEC_JUMP
 	depends on EXPERIMENTAL
 	depends on KEXEC && HIBERNATION
 	---help---
-	  Jump between original kernel and kexeced kernel and invoke
-	  code in physical address mode via KEXEC
+	  Allow to call code through kexec with paging turned off and then
+	  return to the normal kernel. This can be used to call BIOS
+	  code for example, and to implement kexec based hibernation.
+	  Requires uptodate kexec tools.
 
 config PHYSICAL_START
 	hex "Physical address where the kernel is loaded" if (EMBEDDED || CRASH_DUMP)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/