Merge tag 'fsnotify_for_v5.8-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git...

[mirror_ubuntu-jammy-kernel.git] / lib / Kconfig.kgdb

diff --git a/lib/Kconfig.kgdb b/lib/Kconfig.kgdb
index 933680b59e2d9e70a8b4e6c7efdf311dbb59c999..ffa7a76de08604f38ecdd2ee874d8f77cf3ddd7d 100644 (file)
--- a/lib/Kconfig.kgdb
+++ b/lib/Kconfig.kgdb
@@ -124,4 +124,22 @@ config KDB_CONTINUE_CATASTROPHIC
          CONFIG_KDB_CONTINUE_CATASTROPHIC == 2. KDB forces a reboot.
          If you are not sure, say 0.
 
+config ARCH_HAS_EARLY_DEBUG
+       bool
+       default n
+       help
+         If an architecture can definitely handle entering the debugger
+         when early_param's are parsed then it select this config.
+         Otherwise, if "kgdbwait" is passed on the kernel command line it
+         won't actually be processed until dbg_late_init() just after the
+         call to kgdb_arch_late() is made.
+
+         NOTE: Even if this isn't selected by an architecture we will
+         still try to register kgdb to handle breakpoints and crashes
+         when early_param's are parsed, we just won't act on the
+         "kgdbwait" parameter until dbg_late_init().  If you get a
+         crash and try to drop into kgdb somewhere between these two
+         places you might or might not end up being able to use kgdb
+         depending on exactly how far along the architecture has initted.
+
 endif # KGDB