x86, kgdb, init: Add early and late debug states
The kernel debugger can operate well before mm_init(), but the x86 hardware breakpoint code which uses the perf api requires that the kernel allocators are initialized. This means the kernel debug core needs to provide an optional arch specific call back to allow the initialization functions to run after the kernel has been further initialized. The kdb shell already had a similar restriction with an early initialization and late initialization. The kdb_init() was moved into the debug core's version of the late init which is called dbg_late_init(); CC: kgdb-bugreport@lists.sourceforge.net Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
This commit is contained in:
parent
29c843912a
commit
0b4b3827db
4 changed files with 42 additions and 9 deletions
|
@ -78,6 +78,8 @@ static DEFINE_SPINLOCK(kgdb_registration_lock);
|
|||
static int kgdb_con_registered;
|
||||
/* determine if kgdb console output should be used */
|
||||
static int kgdb_use_con;
|
||||
/* Flag for alternate operations for early debugging */
|
||||
bool dbg_is_early = true;
|
||||
/* Next cpu to become the master debug core */
|
||||
int dbg_switch_cpu;
|
||||
|
||||
|
@ -777,11 +779,25 @@ static struct notifier_block kgdb_panic_event_nb = {
|
|||
.priority = INT_MAX,
|
||||
};
|
||||
|
||||
void __weak kgdb_arch_late(void)
|
||||
{
|
||||
}
|
||||
|
||||
void __init dbg_late_init(void)
|
||||
{
|
||||
dbg_is_early = false;
|
||||
if (kgdb_io_module_registered)
|
||||
kgdb_arch_late();
|
||||
kdb_init(KDB_INIT_FULL);
|
||||
}
|
||||
|
||||
static void kgdb_register_callbacks(void)
|
||||
{
|
||||
if (!kgdb_io_module_registered) {
|
||||
kgdb_io_module_registered = 1;
|
||||
kgdb_arch_init();
|
||||
if (!dbg_is_early)
|
||||
kgdb_arch_late();
|
||||
atomic_notifier_chain_register(&panic_notifier_list,
|
||||
&kgdb_panic_event_nb);
|
||||
#ifdef CONFIG_MAGIC_SYSRQ
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue