kgdb: Support late serial drivers; enable early debug w/ boot consoles
Subsystems (9)
Douglas Anderson
reviewerv4 cover kgdb: Support late serial drivers; enable early debug w/ boot consoles
This whole pile of patches was motivated by me trying to get kgdb to work properly on a platform where my serial driver ended up being hit by the -EPROBE_DEFER virus (it wasn't practicing social distancing from other drivers). Specifically my serial driver's parent device depended on a resource that wasn't available when its probe was first called. It returned -EPROBE_DEFER which meant that when "kgdboc" tried to run its setup the serial driver wasn't there. Unfortunately "kgdboc" never tried again, so that meant that kgdb was disabled until I manually enalbed it via sysfs.
While I could try to figure out how to get around the -EPROBE_DEFER somehow, the above problems could happen to anyone and -EPROBE_DEFER is generally considered something you just have to live with. In any case the current "kgdboc" setup is a bit of a race waiting to happen. I _think_ I saw during early testing that even adding a msleep() in the typical serial driver's probe() is enough to trigger similar issues.
I decided that for the above race the best attitude to get kgdb to register at boot was probably "if you can't beat 'em, join 'em". Thus, "kgdboc" now jumps on the -EPROBE_DEFER bandwagon (now that my driver uses it it's no longer a virus). It does so a little awkwardly because "kgdboc" hasn't normally had a "struct device" associated with it, but it's really not _that_ ugly to make a platform device and seems less ugly than alternatives.
Unfortunately now on my system the debugger is one of the last things to register at boot. That's OK for debugging problems that show up significantly after boot, but isn't so hot for all the boot problems that I end up debugging. This motivated me to try to get something working a little earlier.
My first attempt was to try to get the existing "ekgdboc" to work earlier. I tried that for a bit until I realized that it needed to work at the tty layer and I couldn't find any serial drivers that managed to register themselves to the tty layer super early at boot. The only documented use of "ekgdboc" is "ekgdboc=kbd" and that's a bit of a special snowflake. Trying to get my serial driver and all its dependencies to probe normally and register the tty driver super early at boot seemed like a bad way to go. In fact, all the complexity needed to do something like this is why the system already has a special concept of a "boot console" that lives only long enough to transition to the normal console.
Leveraging the boot console seemed like a good way to go and that's what this series does. I found that consoles could have a read() function, though I couldn't find anyone who implemented it. I implemented it for two serial drivers for the devices I had easy access to, making the assumption that for boot consoles that we could assume read() and write() were polling-compatible (seems sane I think).
Now anyone who makes a small change to their serial driver can easily enable early kgdb debugging!
The devices I had for testing were:
- arm32: rk3288-veyron-jerry
- arm64: rk3399-gru-kevin
- arm64: qcom-sc7180-trogdor (not mainline yet)
These are the devices I tested this series on. I tried to test various combinations of enabling/disabling various options and I hopefully caught the corner cases, but I'd appreciate any extra testing people can do. Notably I didn't test on x86, but (I think) I didn't touch much there so I shouldn't have broken anything.
When testing I found a few problems with actually dropping into the debugger super early on arm and arm64 devices. Patches in this series should help with this. For arm I just avoid dropping into the debugger until a little later and for arm64 I actually enable debugging super early.
I realize that bits of this series might feel a little hacky, though I've tried to do things in the cleanest way I could without overly interferring with the rest of the kernel. If you hate the way I solved a problem I would love it if you could provide guidance on how you think I could solve the problem better.
This series (and my comments / documentation / commit messages) are now long enough that my eyes glaze over when I try to read it all over to double-check. I've nontheless tried to double-check it, but I'm pretty sure I did something stupid. Thank you ahead of time for pointing it out to me so I can fix it in v5. If somehow I managed to not do anything stupid (really?) then thank you for double-checking me anyway.
NOTE: v3 of the patch series tacks on support for an extra serial driver from Sumit Garg. I've piled it onto the end of my series at his request just to keep everything together.
Changes in v4:
- ("kgdboc: Remove useless #ifdef...") new for v4.
- Add "if KGDB" to "select ARCH_HAS_EARLY_DEBUG" in Kconfig.
- Add comment about why we always return 0 in kgdboc_earlycon_init().
- Major overhauls to commit message.
- No more #ifdef CONFIG_KGDB_SERIAL_CONSOLE.
- Now keep using bootcon even when the system stops.
- Print "replacing" message before calling deinit().
- earlycon should be static.
- s/The the/The/
Changes in v3:
- ("kgdb: Prevent infinite recursive entries to the debugger") new for v3.
- ("serial: amba-pl011: Support kgdboc_earlycon") pulled into my v3.
- Add deinit() to I/O ops to know a driver can be replaced.
- Added example in kgdb.rst
- Change boolean weak function to KConfig.
- Don't just neuter input, panic if earlycon vanishes.
- No extra param to kgdb_register_io_module().
- Removed unneeded sentence in kerenel-parameters doc.
- Renamed earlycon_kgdboc to kgdboc_earlycon.
- Simplify earlycon_kgdb deinit by using the deinit() function.
- Suggest people use kgdboc_earlycon instead of ekgdboc.
- { ; } ==> { }
Changes in v2:
- ("Revert "kgdboc: disable the console lock when in kgdb"") new for v2.
- ("kgdb: Disable WARN_CONSOLE_UNLOCKED for all kgdb") new for v2.
- Assumes we have ("kgdb: Disable WARN_CONSOLE_UNLOCKED for all kgdb")
- Fix kgdbts, tty/mips_ejtag_fdc, and usb/early/ehci-dbgp
Douglas Anderson (11):
kgdb: Disable WARN_CONSOLE_UNLOCKED for all kgdb
Revert "kgdboc: disable the console lock when in kgdb"
kgdboc: Use a platform device to handle tty drivers showing up late
kgdb: Delay "kgdbwait" to dbg_late_init() by default
arm64: Add call_break_hook() to early_brk64() for early kgdb
kgdb: Prevent infinite recursive entries to the debugger
kgdboc: Remove useless #ifdef CONFIG_KGDB_SERIAL_CONSOLE in kgdboc
kgdboc: Add kgdboc_earlycon to support early kgdb using boot consoles
Documentation: kgdboc: Document new kgdboc_earlycon parameter
serial: qcom_geni_serial: Support kgdboc_earlycon
serial: 8250_early: Support kgdboc_earlycon
Sumit Garg (1):
serial: amba-pl011: Support kgdboc_earlycon
.../admin-guide/kernel-parameters.txt | 20 ++ Documentation/dev-tools/kgdb.rst | 24 ++ arch/arm64/Kconfig | 1 + arch/arm64/include/asm/debug-monitors.h | 2 + arch/arm64/kernel/debug-monitors.c | 2 +- arch/arm64/kernel/traps.c | 3 + arch/x86/Kconfig | 1 + drivers/tty/serial/8250/8250_early.c | 23 ++ drivers/tty/serial/amba-pl011.c | 32 +++ drivers/tty/serial/kgdboc.c | 268 ++++++++++++++++-- drivers/tty/serial/qcom_geni_serial.c | 32 +++ include/linux/kgdb.h | 4 + kernel/debug/debug_core.c | 52 +++- lib/Kconfig.kgdb | 18 ++ 14 files changed, 436 insertions(+), 46 deletions(-)
Signature · 1 line
2.26.2.645.ge9eca65c58-goog
Douglas Anderson
reviewerPATCH v4 1/12 kgdb: Disable WARN_CONSOLE_UNLOCKED for all kgdb
In commit 81eaadcae81b ("kgdboc: disable the console lock when in kgdb") we avoided the WARN_CONSOLE_UNLOCKED() yell when we were in kgdboc. That still works fine, but it turns out that we get a similar yell when using other I/O drivers. One example is the "I/O driver" for the kgdb test suite (kgdbts). When I enabled that I again got the same yells.
Even though "kgdbts" doesn't actually interact with the user over the console, using it still causes kgdb to print to the consoles. That trips the same warning:
con_is_visible+0x60/0x68 con_scroll+0x110/0x1b8 lf+0x4c/0xc8 vt_console_print+0x1b8/0x348 vkdb_printf+0x320/0x89c kdb_printf+0x68/0x90 kdb_main_loop+0x190/0x860 kdb_stub+0x2cc/0x3ec kgdb_cpu_enter+0x268/0x744 kgdb_handle_exception+0x1a4/0x200 kgdb_compiled_brk_fn+0x34/0x44 brk_handler+0x7c/0xb8 do_debug_exception+0x1b4/0x228
Let's increment/decrement the "ignore_console_lock_warning" variable all the time when we enter the debugger.
This will allow us to later revert commit 81eaadcae81b ("kgdboc:
disable the console lock when in kgdb").
---
Changes in v4: None
Changes in v3: None
Changes in v2:
- ("kgdb: Disable WARN_CONSOLE_UNLOCKED for all kgdb") new for v2.
kernel/debug/debug_core.c | 4 ++++ 1 file changed, 4 insertions(+)
kernel/debug/debug_core.c +4 -0
@@ -668,6 +668,8 @@ static int kgdb_cpu_enter(struct kgdb_state *ks, struct pt_regs *regs,if (kgdb_skipexception (ks->ex_vector, ks->linux_regs)) goto kgdb_restore; +atomic_inc (&ignore_console_lock_warning); +/* Call the I/O driver's pre_exception routine */ if (dbg_io_ops->pre_exception) dbg_io_ops->pre_exception ();
@@ -740,6 +742,8 @@ static int kgdb_cpu_enter(struct kgdb_state *ks, struct pt_regs *regs,if (dbg_io_ops->post_exception) dbg_io_ops->post_exception (); +atomic_dec (&ignore_console_lock_warning); +if (!kgdb_single_step) {raw_spin_unlock (&dbg_slave_lock);/* Wait till all the CPUs have quit from the debugger. */
Signature · 1 line
2.26.2.645.ge9eca65c58-goog
Douglas Anderson
reviewerPATCH v4 2/12 Revert "kgdboc: disable the console lock when in kgdb"
In reply to Douglas AndersonThis reverts commit 81eaadcae81b4c1bf01649a3053d1f54e2d81cf1.
Commit 81eaadcae81b ("kgdboc: disable the console lock when in kgdb") is no longer needed now that we have the patch ("kgdb: Disable WARN_CONSOLE_UNLOCKED for all kgdb"). Revert it.
---
Changes in v4: None
Changes in v3: None
Changes in v2:
- ("Revert "kgdboc: disable the console lock when in kgdb"") new for v2.
drivers/tty/serial/kgdboc.c | 4 ---- 1 file changed, 4 deletions(-)
drivers/tty/serial/kgdboc.c +0 -4
@@ -275,14 +275,10 @@ static void kgdboc_pre_exp_handler(void)/* Increment the module count when the debugger is active */ if (!kgdb_connected)try_module_get (THIS_MODULE ); - -atomic_inc (&ignore_console_lock_warning); }static void kgdboc_post_exp_handler (void ) { -atomic_dec (&ignore_console_lock_warning); -/* decrement the module count when the debugger detaches */ if (!kgdb_connected)module_put (THIS_MODULE );
Signature · 1 line
2.26.2.645.ge9eca65c58-goog
Douglas Anderson
reviewerPATCH v4 3/12 kgdboc: Use a platform device to handle tty drivers showing up late
In reply to Douglas AndersonIf you build CONFIG_KGDB_SERIAL_CONSOLE into the kernel then you should be able to have KGDB init itself at bootup by specifying the "kgdboc=..." kernel command line parameter. This has worked OK for me for many years, but on a new device I switched to it stopped working.
The problem is that on this new device the serial driver gets its probe deferred. Now when kgdb initializes it can't find the tty driver and when it gives up it never tries again.
We could try to find ways to move up the initialization of the serial driver and such a thing might be worthwhile, but it's nice to be robust against serial drivers that load late. We could move kgdb to init itself later but that penalizes our ability to debug early boot code on systems where the driver inits early. We could roll our own system of detecting when new tty drivers get loaded and then use that to figure out when kgdb can init, but that's ugly.
Instead, let's jump on the -EPROBE_DEFER bandwagon. We'll create a singleton instance of a "kgdboc" platform device. If we can't find our tty device when the singleton "kgdboc" probes we'll return -EPROBE_DEFER which means that the system will call us back later to try again when the tty device might be there.
We won't fully transition all of the kgdboc to a platform device because early kgdb initialization (via the "ekgdboc" kernel command line parameter) still runs before the platform device has been created. The kgdb platform device is merely used as a convenient way to hook into the system's normal probe deferral mechanisms.
As part of this, we'll ever-so-slightly change how the "kgdboc=..." kernel command line parameter works. Previously if you booted up and kgdb couldn't find the tty driver then later reading '/sys/module/kgdboc/parameters/kgdboc' would return a blank string. Now kgdb will keep track of the string that came as part of the command line and give it back to you. It's expected that this should be an OK change.
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
drivers/tty/serial/kgdboc.c | 126 +++++++++++++++++++++++++++++------- 1 file changed, 101 insertions(+), 25 deletions(-)
drivers/tty/serial/kgdboc.c +101 -25
@@ -20,6 +20,7 @@#include <linux/vt_kern.h> #include <linux/input.h> #include <linux/module.h> +#include <linux/platform_device.h> #define MAX_CONFIG_LEN 40
@@ -27,6 +28,7 @@ static struct kgdb_io kgdboc_io_ops;/* -1 = init not run yet, 0 = unconfigured, 1 = configured. */ static int configured =-1 ; +DEFINE_MUTEX (config_mutex);static char config[MAX_CONFIG_LEN ];static struct kparam_string kps = {
@@ -38,6 +40,8 @@ static int kgdboc_use_kms; /* 1 if we use kernel mode switching */static struct tty_driver *kgdb_tty_driver;static int kgdb_tty_line; +static struct platform_device *kgdboc_pdev; +#ifdef CONFIG_KDB_KEYBOARD static int kgdboc_reset_connect(struct input_handler *handler, struct input_dev *dev,
@@ -133,11 +137,13 @@ static void kgdboc_unregister_kbd(void)static void cleanup_kgdboc (void ) { +if (configured !=1 ) +return ; +if (kgdb_unregister_nmi_console ())return ;kgdboc_unregister_kbd (); -if (configured ==1 ) -kgdb_unregister_io_module (&kgdboc_io_ops); +kgdb_unregister_io_module (&kgdboc_io_ops); }static int configure_kgdboc (void )
@@ -198,20 +204,79 @@ static int configure_kgdboc(void)kgdb_unregister_io_module (&kgdboc_io_ops); noconfig:kgdboc_unregister_kbd (); - config[0 ] =0 ; configured =0 ; -cleanup_kgdboc ();return err; } +static int kgdboc_probe (struct platform_device *pdev) +{ +int ret =0 ; + +mutex_lock (&config_mutex); +if (configured !=1 ) { + ret =configure_kgdboc (); + +/* Convert "no device" to "defer" so we'll keep trying */ +if (ret == -ENODEV ) + ret = -EPROBE_DEFER ; + } +mutex_unlock (&config_mutex); + +return ret; +} + +static struct platform_driver kgdboc_platform_driver = { + .probe = kgdboc_probe, + .driver = { + .name ="kgdboc" , + .suppress_bind_attrs = true, + }, +}; +static int __init init_kgdboc (void ) { -/* Already configured? */ -if (configured ==1 ) +int ret; + +/* +* kgdboc is a little bit of an odd "platform_driver". It can be +* up and running long before the platform_driver object is +* created and thus doesn't actually store anything in it. There's +* only one instance of kgdb so anything is stored as global state. +* The platform_driver is only created so that we can leverage the +* kernel's mechanisms (like -EPROBE_DEFER) to call us when our +* underlying tty is ready. Here we init our platform driver and +* then create the single kgdboc instance. +*/ + ret =platform_driver_register (&kgdboc_platform_driver); +if (ret) +return ret; + + kgdboc_pdev =platform_device_alloc ("kgdboc" ,PLATFORM_DEVID_NONE ); +if (!kgdboc_pdev) { + ret = -ENOMEM ; + goto err_did_register; + } + + ret =platform_device_add (kgdboc_pdev); +if (!ret)return 0 ; -return configure_kgdboc (); +platform_device_put (kgdboc_pdev); + +err_did_register: +platform_driver_unregister (&kgdboc_platform_driver); +return ret; +} + +static void exit_kgdboc (void ) +{ +mutex_lock (&config_mutex); +cleanup_kgdboc (); +mutex_unlock (&config_mutex); + +platform_device_unregister (kgdboc_pdev); +platform_driver_unregister (&kgdboc_platform_driver); }static int kgdboc_get_char (void )
@@ -234,24 +299,20 @@ static int param_set_kgdboc_var(const char *kmessage, const struct kernel_param *kp) {size_t len =strlen (kmessage); +int ret =0 ;if (len >=MAX_CONFIG_LEN ) {pr_err ("config string too long\n" );return -ENOSPC ; } -/* Only copy in the string if the init function has not run yet */ -if (configured <0 ) { -strcpy (config, kmessage); -return 0 ; - } -if (kgdb_connected) {pr_err ("Cannot reconfigure while KGDB is connected.\n" ); -return -EBUSY ; } +mutex_lock (&config_mutex); +strcpy (config, kmessage);/* Chop out \n char as a result of echo */ if (len && config[len -1 ] =='\n' )
@@ -260,8 +321,30 @@ static int param_set_kgdboc_var(const char *kmessage,if (configured ==1 )cleanup_kgdboc (); -/* Go and configure with the new params. */ -return configure_kgdboc (); +/* +* Configure with the new params as long as init already ran. +* Note that we can get called before init if someone loads us +* with "modprobe kgdboc kgdboc=..." or if they happen to use the +* the odd syntax of "kgdboc.kgdboc=..." on the kernel command. +*/ +if (configured >=0 ) + ret =configure_kgdboc (); + +/* +* If we couldn't configure then clear out the config. Note that +* specifying an invalid config on the kernel command line vs. +* through sysfs have slightly different behaviors. If we fail +* to configure what was specified on the kernel command line +* we'll leave it in the 'config' and return -EPROBE_DEFER from +* our probe. When specified through sysfs userspace is +* responsible for loading the tty driver before setting up. +*/ +if (ret) + config[0 ] ='\0' ; + +mutex_unlock (&config_mutex); + +return ret; }static int dbg_restore_graphics;
@@ -320,15 +403,8 @@ __setup("kgdboc=", kgdboc_option_setup);/* This is only available if kgdboc is a built in for early debugging */ static int __init kgdboc_early_init (char *opt) { -/* save the first character of the config string because the -* init routine can destroy it. -*/ -char save_ch; -kgdboc_option_setup (opt); - save_ch = config[0 ]; -init_kgdboc (); - config[0 ] = save_ch; +configure_kgdboc ();return 0 ; }
@@ -336,7 +412,7 @@ early_param("ekgdboc", kgdboc_early_init);#endif /* CONFIG_KGDB_SERIAL_CONSOLE */ module_init (init_kgdboc); -module_exit (cleanup_kgdboc); +module_exit (exit_kgdboc);module_param_call (kgdboc, param_set_kgdboc_var, param_get_string, &kps,0644 );MODULE_PARM_DESC (kgdboc,"<serial_device>[,baud]" );MODULE_DESCRIPTION ("KGDB Console TTY Driver" );
Signature · 1 line
2.26.2.645.ge9eca65c58-goog
Re: [PATCH v4 03/12] kgdboc: Use a platform device to handle tty drivers showing up late
Quoted 62 lines · Douglas Anderson
If you build
CONFIG_KGDB_SERIAL_CONSOLEinto the kernel then you should be able to have KGDB init itself at bootup by specifying the "kgdboc=..." kernel command line parameter. This has worked OK for me for many years, but on a new device I switched to it stopped working.The problem is that on this new device the serial driver gets its probe deferred. Now when kgdb initializes it can't find the tty driver and when it gives up it never tries again.
We could try to find ways to move up the initialization of the serial driver and such a thing might be worthwhile, but it's nice to be robust against serial drivers that load late. We could move kgdb to init itself later but that penalizes our ability to debug early boot code on systems where the driver inits early. We could roll our own system of detecting when new tty drivers get loaded and then use that to figure out when kgdb can init, but that's ugly.
Instead, let's jump on the -EPROBE_DEFER bandwagon. We'll create a singleton instance of a "kgdboc" platform device. If we can't find our tty device when the singleton "kgdboc" probes we'll return -EPROBE_DEFER which means that the system will call us back later to try again when the tty device might be there.
We won't fully transition all of the kgdboc to a platform device because early kgdb initialization (via the "ekgdboc" kernel command line parameter) still runs before the platform device has been created. The kgdb platform device is merely used as a convenient way to hook into the system's normal probe deferral mechanisms.
As part of this, we'll ever-so-slightly change how the "kgdboc=..." kernel command line parameter works. Previously if you booted up and kgdb couldn't find the tty driver then later reading '
/sys/module/kgdboc/parameters/kgdboc' would return a blank string. Now kgdb will keep track of the string that came as part of the command line and give it back to you. It's expected that this should be an OK change.Signed-off-by Douglas Anderson <[email protected]>Reviewed-by Greg Kroah-Hartman <[email protected]>Reviewed-by Daniel Thompson <[email protected]>---
Changes in v4: None
Changes in v3: None
Changes in v2: Nonedrivers/tty/serial/kgdboc.c | 126 +++++++++++++++++++++++++++++------- 1 file changed, 101 insertions(+), 25 deletions(-)drivers/tty/serial/kgdboc.c +1
-0@@ -20,6 +20,7 @@#include <linux/vt_kern.h> #include <linux/input.h> #include <linux/module.h> +#include <linux/platform_device.h> #define MAX_CONFIG_LEN 40
drivers/tty/serial/kgdboc.c static struct kgdb_io kgdboc_io_ops; · line 31
Quoted 4 lines
drivers/tty/serial/kgdboc.c +1
-0@@ -27,6 +28,7 @@ static struct kgdb_io kgdboc_io_ops;/* -1 = init not run yet, 0 = unconfigured, 1 = configured. */ static int configured =-1 ; +DEFINE_MUTEX (config_mutex);
Sparse gently pointed out to me that this should be static. Don't worry about it though... I will fixup.
Daniel.
Quoted 203 lines
drivers/tty/serial/kgdboc.c +99
-25static char config[MAX_CONFIG_LEN ];static struct kparam_string kps = {@@ -38,6 +40,8 @@ static int kgdboc_use_kms; /* 1 if we use kernel mode switching */static struct tty_driver *kgdb_tty_driver;static int kgdb_tty_line; +static struct platform_device *kgdboc_pdev; +#ifdef CONFIG_KDB_KEYBOARD static int kgdboc_reset_connect(struct input_handler *handler, struct input_dev *dev,@@ -133,11 +137,13 @@ static void kgdboc_unregister_kbd(void)static void cleanup_kgdboc (void ) { +if (configured !=1 ) +return ; +if (kgdb_unregister_nmi_console ())return ;kgdboc_unregister_kbd (); -if (configured ==1 ) -kgdb_unregister_io_module (&kgdboc_io_ops); +kgdb_unregister_io_module (&kgdboc_io_ops); }static int configure_kgdboc (void )@@ -198,20 +204,79 @@ static int configure_kgdboc(void)kgdb_unregister_io_module (&kgdboc_io_ops); noconfig:kgdboc_unregister_kbd (); - config[0 ] =0 ; configured =0 ; -cleanup_kgdboc ();return err; } +static int kgdboc_probe (struct platform_device *pdev) +{ +int ret =0 ; + +mutex_lock (&config_mutex); +if (configured !=1 ) { + ret =configure_kgdboc (); + +/* Convert "no device" to "defer" so we'll keep trying */ +if (ret == -ENODEV ) + ret = -EPROBE_DEFER ; + } +mutex_unlock (&config_mutex); + +return ret; +} + +static struct platform_driver kgdboc_platform_driver = { + .probe = kgdboc_probe, + .driver = { + .name ="kgdboc" , + .suppress_bind_attrs = true, + }, +}; +static int __init init_kgdboc (void ) { -/* Already configured? */ -if (configured ==1 ) +int ret; + +/* +* kgdboc is a little bit of an odd "platform_driver". It can be +* up and running long before the platform_driver object is +* created and thus doesn't actually store anything in it. There's +* only one instance of kgdb so anything is stored as global state. +* The platform_driver is only created so that we can leverage the +* kernel's mechanisms (like -EPROBE_DEFER) to call us when our +* underlying tty is ready. Here we init our platform driver and +* then create the single kgdboc instance. +*/ + ret =platform_driver_register (&kgdboc_platform_driver); +if (ret) +return ret; + + kgdboc_pdev =platform_device_alloc ("kgdboc" ,PLATFORM_DEVID_NONE ); +if (!kgdboc_pdev) { + ret = -ENOMEM ; + goto err_did_register; + } + + ret =platform_device_add (kgdboc_pdev); +if (!ret)return 0 ; -return configure_kgdboc (); +platform_device_put (kgdboc_pdev); + +err_did_register: +platform_driver_unregister (&kgdboc_platform_driver); +return ret; +} + +static void exit_kgdboc (void ) +{ +mutex_lock (&config_mutex); +cleanup_kgdboc (); +mutex_unlock (&config_mutex); + +platform_device_unregister (kgdboc_pdev); +platform_driver_unregister (&kgdboc_platform_driver); }static int kgdboc_get_char (void )@@ -234,24 +299,20 @@ static int param_set_kgdboc_var(const char *kmessage, const struct kernel_param *kp) {size_t len =strlen (kmessage); +int ret =0 ;if (len >=MAX_CONFIG_LEN ) {pr_err ("config string too long\n" );return -ENOSPC ; } -/* Only copy in the string if the init function has not run yet */ -if (configured <0 ) { -strcpy (config, kmessage); -return 0 ; - } -if (kgdb_connected) {pr_err ("Cannot reconfigure while KGDB is connected.\n" ); -return -EBUSY ; } +mutex_lock (&config_mutex); +strcpy (config, kmessage);/* Chop out \n char as a result of echo */ if (len && config[len -1 ] =='\n' )@@ -260,8 +321,30 @@ static int param_set_kgdboc_var(const char *kmessage,if (configured ==1 )cleanup_kgdboc (); -/* Go and configure with the new params. */ -return configure_kgdboc (); +/* +* Configure with the new params as long as init already ran. +* Note that we can get called before init if someone loads us +* with "modprobe kgdboc kgdboc=..." or if they happen to use the +* the odd syntax of "kgdboc.kgdboc=..." on the kernel command. +*/ +if (configured >=0 ) + ret =configure_kgdboc (); + +/* +* If we couldn't configure then clear out the config. Note that +* specifying an invalid config on the kernel command line vs. +* through sysfs have slightly different behaviors. If we fail +* to configure what was specified on the kernel command line +* we'll leave it in the 'config' and return -EPROBE_DEFER from +* our probe. When specified through sysfs userspace is +* responsible for loading the tty driver before setting up. +*/ +if (ret) + config[0 ] ='\0' ; + +mutex_unlock (&config_mutex); + +return ret; }static int dbg_restore_graphics;@@ -320,15 +403,8 @@ __setup("kgdboc=", kgdboc_option_setup);/* This is only available if kgdboc is a built in for early debugging */ static int __init kgdboc_early_init (char *opt) { -/* save the first character of the config string because the -* init routine can destroy it. -*/ -char save_ch; -kgdboc_option_setup (opt); - save_ch = config[0 ]; -init_kgdboc (); - config[0 ] = save_ch; +configure_kgdboc ();return 0 ; }@@ -336,7 +412,7 @@ early_param("ekgdboc", kgdboc_early_init);#endif /* CONFIG_KGDB_SERIAL_CONSOLE */ module_init (init_kgdboc); -module_exit (cleanup_kgdboc); +module_exit (exit_kgdboc);module_param_call (kgdboc, param_set_kgdboc_var, param_get_string, &kps,0644 );MODULE_PARM_DESC (kgdboc,"<serial_device>[,baud]" );MODULE_DESCRIPTION ("KGDB Console TTY Driver" );Signature · 1 line
2.26.2.645.ge9eca65c58-goog
Douglas Anderson
reviewerPATCH v4 4/12 kgdb: Delay "kgdbwait" to dbg_late_init() by default
In reply to Douglas AndersonUsing kgdb requires at least some level of architecture-level initialization. If nothing else, it relies on the architecture to pass breakpoints / crashes onto kgdb.
On some architectures this all works super early, specifically it starts working at some point in time before Linux parses early_params's. On other architectures it doesn't. A survey of a few platforms:
a) x86: Presumably it all works early since "ekgdboc" is documented to work here.
b) arm64: Catching crashes works; with a simple patch breakpoints can also be made to work.
c) arm: Nothing in kgdb works until
paging_init() -> devicemaps_init() -> early_trap_init()
Let's be conservative and, by default, process "kgdbwait" (which tells the kernel to drop into the debugger ASAP at boot) a bit later at dbg_late_init() time. If an architecture has tested it and wants to re-enable super early debugging, they can select the ARCH_HAS_EARLY_DEBUG KConfig option. We'll do this for x86 to start. It should be noted that dbg_late_init() is still called quite early in the system.
Note that this patch doesn't affect when kgdb runs its init. If kgdb is set to initialize early it will still initialize when parsing early_param's. This patch _only_ inhibits the initial breakpoint from "kgdbwait". This means:
* Without any extra patches arm64 platforms will at least catch crashes after kgdb inits.
* arm platforms will catch crashes (and could handle a hardcoded kgdb_breakpoint()) any time after early_trap_init() runs, even before dbg_late_init().
---
Changes in v4:
- Add "if KGDB" to "select ARCH_HAS_EARLY_DEBUG" in Kconfig.
Changes in v3:
- Change boolean weak function to KConfig.
Changes in v2: None
arch/x86/Kconfig | 1 + kernel/debug/debug_core.c | 25 +++++++++++++++---------- lib/Kconfig.kgdb | 18 ++++++++++++++++++ 3 files changed, 34 insertions(+), 10 deletions(-)
arch/x86/Kconfig +1 -0
@@ -60,6 +60,7 @@ config X86 select ARCH_HAS_ACPI_TABLE_UPGRADE if ACPI select ARCH_HAS_DEBUG_VIRTUAL select ARCH_HAS_DEVMEM_IS_ALLOWED + select ARCH_HAS_EARLY_DEBUG if KGDB select ARCH_HAS_ELF_RANDOMIZE select ARCH_HAS_FAST_MULTIPLIER select ARCH_HAS_FILTER_PGPROT
kernel/debug/debug_core.c +15 -10
@@ -950,6 +950,14 @@ void kgdb_panic(const char *msg)kgdb_breakpoint (); } +static void kgdb_initial_breakpoint (void ) +{ + kgdb_break_asap =0 ; + +pr_crit ("Waiting for connection from remote gdb...\n" ); +kgdb_breakpoint (); +} +void __weak kgdb_arch_late (void ) { }
@@ -960,6 +968,9 @@ void __init dbg_late_init(void)if (kgdb_io_module_registered)kgdb_arch_late ();kdb_init (KDB_INIT_FULL ); + +if (kgdb_io_module_registered && kgdb_break_asap) +kgdb_initial_breakpoint (); } static int
@@ -1055,14 +1066,6 @@ void kgdb_schedule_breakpoint(void) }EXPORT_SYMBOL_GPL (kgdb_schedule_breakpoint); -static void kgdb_initial_breakpoint (void ) -{ - kgdb_break_asap =0 ; - -pr_crit ("Waiting for connection from remote gdb...\n" ); -kgdb_breakpoint (); -} -/** * kgdb_register_io_module - register KGDB IO module * @new_dbg_io_ops: the io ops vector
@@ -1099,7 +1102,8 @@ int kgdb_register_io_module(struct kgdb_io *new_dbg_io_ops)/* Arm KGDB now. */ kgdb_register_callbacks (); -if (kgdb_break_asap) +if (kgdb_break_asap && + (!dbg_is_early ||IS_ENABLED (CONFIG_ARCH_HAS_EARLY_DEBUG )))kgdb_initial_breakpoint ();return 0 ;
@@ -1169,7 +1173,8 @@ static int __init opt_kgdb_wait(char *str) kgdb_break_asap =1 ;kdb_init (KDB_INIT_EARLY ); -if (kgdb_io_module_registered) +if (kgdb_io_module_registered && +IS_ENABLED (CONFIG_ARCH_HAS_EARLY_DEBUG ))kgdb_initial_breakpoint ();return 0 ;
lib/Kconfig.kgdb +18 -0
@@ -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
Signature · 1 line
2.26.2.645.ge9eca65c58-goog
Re: [PATCH v4 04/12] kgdb: Delay "kgdbwait" to dbg_late_init() by default
Quoted 35 lines · Douglas Anderson
Using kgdb requires at least some level of architecture-level initialization. If nothing else, it relies on the architecture to pass breakpoints / crashes onto kgdb.
On some architectures this all works super early, specifically it starts working at some point in time before Linux parses early_params's. On other architectures it doesn't. A survey of a few platforms:
a) x86: Presumably it all works early since "ekgdboc" is documented to work here.
b) arm64: Catching crashes works; with a simple patch breakpoints can also be made to work.
c) arm: Nothing in kgdb works until
paging_init()->devicemaps_init()->early_trap_init()Let's be conservative and, by default, process "kgdbwait" (which tells the kernel to drop into the debugger ASAP at boot) a bit later at
dbg_late_init()time. If an architecture has tested it and wants to re-enable super early debugging, they can select theARCH_HAS_EARLY_DEBUGKConfig option. We'll do this for x86 to start. It should be noted thatdbg_late_init()is still called quite early in the system.Note that this patch doesn't affect when kgdb runs its init. If kgdb is set to initialize early it will still initialize when parsing early_param's. This patch _only_ inhibits the initial breakpoint from "kgdbwait". This means:
* Without any extra patches arm64 platforms will at least catch crashes after kgdb inits.
* arm platforms will catch crashes (and could handle a hardcodedkgdb_breakpoint()) any time afterearly_trap_init()runs, even beforedbg_late_init().
Quoted 5 lines
Signed-off-by Douglas Anderson <[email protected]>Cc Thomas Gleixner <[email protected]>Cc Ingo Molnar <[email protected]>Cc Borislav Petkov <[email protected]>Reviewed-by Greg Kroah-Hartman <[email protected]>
I hope to pull this set into the kgdb tree shortly. Any objections to the arch/x86 changes this would bring?
Daniel.
Quoted 121 lines
---
Changes in v4:
- Add "if KGDB" to "selectARCH_HAS_EARLY_DEBUG" inKconfig.Changes in v3:
- Change boolean weak function to KConfig.Changes in v2: None
arch/x86/Kconfig | 1 + kernel/debug/debug_core.c | 25 +++++++++++++++---------- lib/Kconfig.kgdb | 18 ++++++++++++++++++ 3 files changed, 34 insertions(+), 10 deletions(-)arch/x86/Kconfig +1
-0@@ -60,6 +60,7 @@ config X86 select ARCH_HAS_ACPI_TABLE_UPGRADE if ACPI select ARCH_HAS_DEBUG_VIRTUAL select ARCH_HAS_DEVMEM_IS_ALLOWED + select ARCH_HAS_EARLY_DEBUG if KGDB select ARCH_HAS_ELF_RANDOMIZE select ARCH_HAS_FAST_MULTIPLIER select ARCH_HAS_FILTER_PGPROTkernel/debug/debug_core.c +15
-10@@ -950,6 +950,14 @@ void kgdb_panic(const char *msg)kgdb_breakpoint (); } +static void kgdb_initial_breakpoint (void ) +{ + kgdb_break_asap =0 ; + +pr_crit ("Waiting for connection from remote gdb...\n" ); +kgdb_breakpoint (); +} +void __weak kgdb_arch_late (void ) { }@@ -960,6 +968,9 @@ void __init dbg_late_init(void)if (kgdb_io_module_registered)kgdb_arch_late ();kdb_init (KDB_INIT_FULL ); + +if (kgdb_io_module_registered && kgdb_break_asap) +kgdb_initial_breakpoint (); } static int@@ -1055,14 +1066,6 @@ void kgdb_schedule_breakpoint(void) }EXPORT_SYMBOL_GPL (kgdb_schedule_breakpoint); -static void kgdb_initial_breakpoint (void ) -{ - kgdb_break_asap =0 ; - -pr_crit ("Waiting for connection from remote gdb...\n" ); -kgdb_breakpoint (); -} -/** * kgdb_register_io_module - register KGDB IO module * @new_dbg_io_ops: the io ops vector @@ -1099,7 +1102,8 @@ int kgdb_register_io_module(struct kgdb_io *new_dbg_io_ops)/* Arm KGDB now. */ kgdb_register_callbacks (); -if (kgdb_break_asap) +if (kgdb_break_asap && + (!dbg_is_early ||IS_ENABLED (CONFIG_ARCH_HAS_EARLY_DEBUG )))kgdb_initial_breakpoint ();return 0 ;@@ -1169,7 +1173,8 @@ static int __init opt_kgdb_wait(char *str) kgdb_break_asap =1 ;kdb_init (KDB_INIT_EARLY ); -if (kgdb_io_module_registered) +if (kgdb_io_module_registered && +IS_ENABLED (CONFIG_ARCH_HAS_EARLY_DEBUG ))kgdb_initial_breakpoint ();return 0 ;lib/Kconfig.kgdb +18
-0@@ -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 # KGDBSignature · 1 line
2.26.2.645.ge9eca65c58-goog
Douglas Anderson
reviewerPATCH v4 5/12 arm64: Add call_break_hook() to early_brk64() for early kgdb
In reply to Douglas AndersonIn order to make early kgdb work properly we need early_brk64() to be able to call into it. This is as easy as adding a call into call_break_hook() just like we do later in the normal brk_handler().
Once we do this we can let kgdb know that it can break into the debugger a little earlier (specifically when parsing early_param's).
NOTE: without this patch it turns out that arm64 can't do breakpoints even at dbg_late_init(), so if we decide something about this patch is wrong we might need to move dbg_late_init() a little later.
---
Changes in v4:
- Add "if KGDB" to "select ARCH_HAS_EARLY_DEBUG" in Kconfig.
Changes in v3:
- Change boolean weak function to KConfig.
Changes in v2: None
arch/arm64/Kconfig | 1 + arch/arm64/include/asm/debug-monitors.h | 2 ++ arch/arm64/kernel/debug-monitors.c | 2 +- arch/arm64/kernel/traps.c | 3 +++ 4 files changed, 7 insertions(+), 1 deletion(-)
arch/arm64/Kconfig +1 -0
@@ -13,6 +13,7 @@ config ARM64 select ARCH_HAS_DEVMEM_IS_ALLOWED select ARCH_HAS_DMA_PREP_COHERENT select ARCH_HAS_ACPI_TABLE_UPGRADE if ACPI + select ARCH_HAS_EARLY_DEBUG if KGDB select ARCH_HAS_FAST_MULTIPLIER select ARCH_HAS_FORTIFY_SOURCE select ARCH_HAS_GCOV_PROFILE_ALL
arch/arm64/include/asm/debug-monitors.h +2 -0
@@ -97,6 +97,8 @@ void unregister_user_break_hook(struct break_hook *hook);void register_kernel_break_hook (struct break_hook *hook);void unregister_kernel_break_hook (struct break_hook *hook); +int call_break_hook (struct pt_regs *regs,unsigned int esr); +u8 debug_monitors_arch (void );enum dbg_active_el {
arch/arm64/kernel/debug-monitors.c +1 -1
@@ -297,7 +297,7 @@ void unregister_kernel_break_hook(struct break_hook *hook)unregister_debug_hook (&hook->node); } -static int call_break_hook (struct pt_regs *regs,unsigned int esr) +int call_break_hook (struct pt_regs *regs,unsigned int esr) {struct break_hook *hook;struct list_head *list;
arch/arm64/kernel/traps.c +3 -0
@@ -1044,6 +1044,9 @@ int __init early_brk64(unsigned long addr, unsigned int esr,if ((comment & ~KASAN_BRK_MASK ) ==KASAN_BRK_IMM )return kasan_handler (regs, esr) !=DBG_HOOK_HANDLED ;#endif +if (call_break_hook (regs, esr) ==DBG_HOOK_HANDLED ) +return 0 ; +return bug_handler (regs, esr) !=DBG_HOOK_HANDLED ; }
Signature · 7 lines
2.26.2.645.ge9eca65c58-goog _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Doug Anderson
reviewerRe: [PATCH v4 05/12] arm64: Add call_break_hook() to early_brk64() for early kgdb
Hi,
Quoted 25 lines · Douglas Anderson
In order to make early kgdb work properly we need
early_brk64()to be able to call into it. This is as easy as adding a call intocall_break_hook()just like we do later in the normalbrk_handler().Once we do this we can let kgdb know that it can break into the debugger a little earlier (specifically when parsing early_param's).
NOTE: without this patch it turns out that arm64 can't do breakpoints even at
dbg_late_init(), so if we decide something about this patch is wrong we might need to movedbg_late_init()a little later.Signed-off-by Douglas Anderson <[email protected]>Cc Catalin Marinas <[email protected]>Cc Will Deacon <[email protected]>Reviewed-by Greg Kroah-Hartman <[email protected]>Reviewed-by Daniel Thompson <[email protected]>---
Changes in v4:
- Add "if KGDB" to "selectARCH_HAS_EARLY_DEBUG" inKconfig.Changes in v3:
- Change boolean weak function to KConfig.
Quoted 7 lines
Changes in v2: None
arch/arm64/Kconfig | 1 + arch/arm64/include/asm/debug-monitors.h | 2 ++ arch/arm64/kernel/debug-monitors.c | 2 +- arch/arm64/kernel/traps.c | 3 +++ 4 files changed, 7 insertions(+), 1 deletion(-)
As discussed in the replies to the v3 version of this patch [1], I have posted a replacement patch for this one [2]. After the cut in the replacement patch I talk about different ways it could land. Hopefully that's not too confusing. I can also re-spam everyone with a v5 of the whole series if that makes it clearer.
[1] https://lore.kernel.org/r/20200428141218.v3.5.I22067ad43e77ddfd4b64c2d49030628480f9e8d9@changeid
[2] https://lore.kernel.org/r/20200513160501.1.I0b5edf030cc6ebef6ab4829f8867cdaea42485d8@changeid
-Doug
Douglas Anderson
reviewerPATCH v4 6/12 kgdb: Prevent infinite recursive entries to the debugger
In reply to Douglas AndersonIf we detect that we recursively entered the debugger we should hack our I/O ops to NULL so that the panic() in the next line won't actually cause another recursion into the debugger. The first line of kgdb_panic() will check this and return.
---
Changes in v4: None
Changes in v3:
- ("kgdb: Prevent infinite recursive entries to the debugger") new for v3.
Changes in v2: None
kernel/debug/debug_core.c | 1 + 1 file changed, 1 insertion(+)
kernel/debug/debug_core.c +1 -0
@@ -532,6 +532,7 @@ static int kgdb_reenter_check(struct kgdb_state *ks)if (exception_level >1 ) {dump_stack (); + kgdb_io_module_registered = false;panic ("Recursive entry to debugger" ); }
Signature · 1 line
2.26.2.645.ge9eca65c58-goog
Douglas Anderson
reviewerPATCH v4 7/12 kgdboc: Remove useless #ifdef CONFIG_KGDB_SERIAL_CONSOLE in kgdboc
In reply to Douglas AndersonThis file is only ever compiled if that config is on since the Makefile says:
obj-$(CONFIG_KGDB_SERIAL_CONSOLE) += kgdboc.o
Let's get rid of the useless #ifdef.
---
Changes in v4:
- ("kgdboc: Remove useless #ifdef...") new for v4.
Changes in v3: None
Changes in v2: None
drivers/tty/serial/kgdboc.c | 2 -- 1 file changed, 2 deletions(-)
drivers/tty/serial/kgdboc.c +0 -2
@@ -380,7 +380,6 @@ static struct kgdb_io kgdboc_io_ops = { .post_exception = kgdboc_post_exp_handler, }; -#ifdef CONFIG_KGDB_SERIAL_CONSOLE static int kgdboc_option_setup (char *opt) {if (!opt) {
@@ -409,7 +408,6 @@ static int __init kgdboc_early_init(char *opt) }early_param ("ekgdboc" , kgdboc_early_init); -#endif /* CONFIG_KGDB_SERIAL_CONSOLE */ module_init (init_kgdboc);module_exit (exit_kgdboc);
Signature · 1 line
2.26.2.645.ge9eca65c58-goog
Re: [PATCH v4 07/12] kgdboc: Remove useless #ifdef CONFIG_KGDB_SERIAL_CONSOLE in kgdboc
Quoted 9 lines · Douglas Anderson
This file is only ever compiled if that config is on since the
Makefilesays:obj-$(CONFIG_KGDB_SERIAL_CONSOLE) += kgdboc.oLet's get rid of the useless #ifdef.
Reported-by Daniel Thompson <[email protected]>Signed-off-by Douglas Anderson <[email protected]>
Quoted 34 lines
---
Changes in v4:
- ("kgdboc: Remove useless #ifdef...") new for v4.Changes in v3: None
Changes in v2: Nonedrivers/tty/serial/kgdboc.c | 2 -- 1 file changed, 2 deletions(-)drivers/tty/serial/kgdboc.c +0
-2@@ -380,7 +380,6 @@ static struct kgdb_io kgdboc_io_ops = { .post_exception = kgdboc_post_exp_handler, }; -#ifdef CONFIG_KGDB_SERIAL_CONSOLE static int kgdboc_option_setup (char *opt) {if (!opt) {@@ -409,7 +408,6 @@ static int __init kgdboc_early_init(char *opt) }early_param ("ekgdboc" , kgdboc_early_init); -#endif /* CONFIG_KGDB_SERIAL_CONSOLE */ module_init (init_kgdboc);module_exit (exit_kgdboc);Signature · 1 line
2.26.2.645.ge9eca65c58-goog
Douglas Anderson
reviewerPATCH v4 8/12 kgdboc: Add kgdboc_earlycon to support early kgdb using boot consoles
In reply to Douglas AndersonWe want to enable kgdb to debug the early parts of the kernel. Unfortunately kgdb normally is a client of the tty API in the kernel and serial drivers don't register to the tty layer until fairly late in the boot process.
Serial drivers do, however, commonly register a boot console. Let's enable the kgdboc driver to work with boot consoles to provide early debugging.
This change co-opts the existing read() function pointer that's part of "struct console". It's assumed that if a boot console (with the flag CON_BOOT) has implemented read() that both the read() and write() function are polling functions. That means they work without interrupts and read() will return immediately (with 0 bytes read) if there's nothing to read. This should be a safe assumption since it appears that no current boot consoles implement read() right now and there seems no reason to do so unless they wanted to support "kgdboc_earlycon".
The normal/expected way to make all this work is to use "kgdboc_earlycon" and "kgdboc" together. You should point them both to the same physical serial connection. At boot time, as the system transitions from the boot console to the normal console (and registers a tty), kgdb will switch over.
One awkward part of all this, though, is that there can be a window where the boot console goes away and we can't quite transtion over to the main kgdboc that uses the tty layer. There are two main problems:
1. The act of registering the tty doesn't cause any call into kgdboc so there is a window of time when the tty is there but kgdboc's init code hasn't been called so we can't transition to it.
2. On some serial drivers the normal console inits (and replaces the boot console) quite early in the system. Presumably these drivers were coded up before earlycon worked as well as it does today and probably they don't need to do this anymore, but it causes us problems nontheless.
Problem #1 is not too big of a deal somewhat due to the luck of probe ordering. kgdboc is last in the tty/serial/Makefile so its probe gets right after all other tty devices. It's not fun to rely on this, but it does work for the most part.
Problem #2 is a big deal, but only for some serial drivers. Other serial drivers end up registering the console (which gets rid of the boot console) and tty at nearly the same time.
The way we'll deal with the window when the system has stopped using the boot console and the time when we're setup using the tty is to keep using the boot console. This may sound surprising, but it has been found to work well in practice. If it doesn't work, it shouldn't be too hard for a given serial driver to make it keep working. Specifically, it's expected that the read()/write() function provided in the boot console should be the same (or nearly the same) as the normal kgdb polling functions. That means continuing to use them should work just fine. To make things even more likely to work work we'll also trap the recently added exit() function in the boot console we're using and delay any calls to it until we're all done with the boot console.
NOTE: there could be ways to use all this in weird / unexpected ways. If you do something like this, it's a bit of a buyer beware situation. Specifically:
- If you specify only "kgdboc_earlycon" but not "kgdboc" then (depending on your serial driver) things will probably work OK, but you'll get a warning printed the first time you use kgdb after the boot console is gone. You'd only be able to do this, of course, if the serial driver you're running atop provided an early boot console.
- If your "kgdboc_earlycon" and "kgdboc" devices are not the same device things should work OK, but it'll be your job to switch over which device you're monitoring (including figuring out how to switch over gdb in-flight if you're using it).
When trying to enable "kgdboc_earlycon" it should be noted that the names that are registered through the boot console layer and the tty layer are not the same for the same port. For example when debugging on one board I'd need to pass "kgdboc_earlycon=qcom_geni kgdboc=ttyMSM0" to enable things properly. Since digging up the boot console name is a pain and there will rarely be more than one boot console enabled, you can provide the "kgdboc_earlycon" parameter without specifying the name of the boot console. In this case we'll just pick the first boot that implements read() that we find.
This new "kgdboc_earlycon" parameter should be contrasted to the existing "ekgdboc" parameter. While both provide a way to debug very early, the usage and mechanisms are quite different. Specifically "kgdboc_earlycon" is meant to be used in tandem with "kgdboc" and there is a transition from one to the other. The "ekgdboc" parameter, on the other hand, replaces the "kgdboc" parameter. It runs the same logic as the "kgdboc" parameter but just relies on your TTY driver being present super early. The only known usage of the old "ekgdboc" parameter is documented as "ekgdboc=kbd earlyprintk=vga". It should be noted that "kbd" has special treatment allowing it to init early as a tty device.
---
I have kept Greg's Reviewed-by and Sumit's Tested-by tags on this commit despite changes that aren't totally trivial. Please yell if you disagree with this. Reasons:
- Greg's Reviewed-by seemed more an overall acknowledgment that the series wasn't totally insane rather than a detailed review. I don't think the changes from v2 to v3 change that. The changes from v3 to v4 include a little extra craziness and I considered removing the tag but I don't think it affects the overall concept so I kept it.
- Sumit's Tested-by seemed useful as confirmation that someone else made this work on a machine that wasn't mine. I don't believe that the changes from v2 to v4 should affect anything here.
Also note that this incorporates ideas and a bit of code that Daniel posted on the list. Daniel: I'll leave it up to you if you want to add a "Co-Developed-by" credit.
Changes in v4:
- Add comment about why we always return 0 in kgdboc_earlycon_init().
- Major overhauls to commit message.
- No more #ifdef CONFIG_KGDB_SERIAL_CONSOLE.
- Now keep using bootcon even when the system stops.
- Print "replacing" message before calling deinit().
- earlycon should be static.
Changes in v3:
- Add deinit() to I/O ops to know a driver can be replaced.
- Don't just neuter input, panic if earlycon vanishes.
- No extra param to kgdb_register_io_module().
- Renamed earlycon_kgdboc to kgdboc_earlycon.
- Simplify earlycon_kgdb deinit by using the deinit() function.
Changes in v2:
- Assumes we have ("kgdb: Disable WARN_CONSOLE_UNLOCKED for all kgdb")
- Fix kgdbts, tty/mips_ejtag_fdc, and usb/early/ehci-dbgp
drivers/tty/serial/kgdboc.c | 136 ++++++++++++++++++++++++++++++++++++ include/linux/kgdb.h | 4 ++ kernel/debug/debug_core.c | 22 ++++-- 3 files changed, 158 insertions(+), 4 deletions(-)
drivers/tty/serial/kgdboc.c +136 -0
@@ -21,6 +21,7 @@#include <linux/input.h> #include <linux/module.h> #include <linux/platform_device.h> +#include <linux/serial_core.h> #define MAX_CONFIG_LEN 40
@@ -42,6 +43,10 @@ static int kgdb_tty_line;static struct platform_device *kgdboc_pdev; +static struct kgdb_io kgdboc_earlycon_io_ops; +static struct console *earlycon; +static int (*earlycon_orig_exit)(struct console *con); +#ifdef CONFIG_KDB_KEYBOARD static int kgdboc_reset_connect(struct input_handler *handler, struct input_dev *dev,
@@ -137,6 +142,9 @@ static void kgdboc_unregister_kbd(void)static void cleanup_kgdboc (void ) { +if (earlycon) +kgdb_unregister_io_module (&kgdboc_earlycon_io_ops); +if (configured !=1 )return ;
@@ -409,6 +417,134 @@ static int __init kgdboc_early_init(char *opt)early_param ("ekgdboc" , kgdboc_early_init); +static int kgdboc_earlycon_get_char (void ) +{ +char c; + +if (!earlycon->read (earlycon, &c,1 )) +return NO_POLL_CHAR ; + +return c; +} + +static void kgdboc_earlycon_put_char (u8 chr) +{ + earlycon->write (earlycon, &chr,1 ); +} + +static void kgdboc_earlycon_pre_exp_handler (void ) +{ +struct console *con; +static bool already_warned; + +if (already_warned) +return ; + +/* +* When the first normal console comes up the kernel will take all +* the boot consoles out of the list. Really, we should stop using +* the boot console when it does that but until a TTY is registered +* we have no other choice so we keep using it. Since not all +* serial drivers might be OK with this, print a warning once per +* boot if we detect this case. +*/ +for_each_console (con) +if (con == earlycon) +return ; + + already_warned = true; +pr_warn ("kgdboc_earlycon is still using bootconsole\n" ); +} + +static int kgdboc_earlycon_deferred_exit (struct console *con) +{ +/* +* If we get here it means the boot console is going away but we +* don't yet have a suitable replacement. Don't pass through to +* the original exit routine. We'll call it later in our deinit() +* function. For now, restore the original exit() function pointer +* as a sentinal that we've hit this point. +*/ + con->exit = earlycon_orig_exit; + +return 0 ; +} + +static void kgdboc_earlycon_deinit (void ) +{ +if (!earlycon) +return ; + +if (earlycon->exit == kgdboc_earlycon_deferred_exit) +/* +* kgdboc_earlycon is exiting but original boot console exit +* was never called (AKA kgdboc_earlycon_deferred_exit() +* didn't ever run). Undo our trap. +*/ + earlycon->exit = earlycon_orig_exit; +else if (earlycon->exit) +/* +* We skipped calling the exit() routine so we could try to +* keep using the boot console even after it went away. We're +* finally done so call the function now. +*/ + earlycon->exit (earlycon); + + earlycon =NULL ; +} + +static struct kgdb_io kgdboc_earlycon_io_ops = { + .name ="kgdboc_earlycon" , + .read_char = kgdboc_earlycon_get_char, + .write_char = kgdboc_earlycon_put_char, + .pre_exception = kgdboc_earlycon_pre_exp_handler, + .deinit = kgdboc_earlycon_deinit, + .is_console = true, +}; + +static int __init kgdboc_earlycon_init (char *opt) +{ +struct console *con; + +kdb_init (KDB_INIT_EARLY ); + +/* +* Look for a matching console, or if the name was left blank just +* pick the first one we find. +*/ +console_lock (); +for_each_console (con) { +if (con->write && con->read && + (con->flags & (CON_BOOT |CON_ENABLED )) && + (!opt || !opt[0 ] ||strcmp (con->name, opt) ==0 )) +break ; + } + +if (!con) { +pr_info ("Couldn't find kgdb earlycon\n" ); + goto unlock; + } + + earlycon = con; +pr_info ("Going to register kgdb with earlycon '%s'\n" , con->name); +if (kgdb_register_io_module (&kgdboc_earlycon_io_ops) !=0 ) { + earlycon =NULL ; +pr_info ("Failed to register kgdb with earlycon\n" ); + }else { +/* Trap exit so we can keep earlycon longer if needed. */ + earlycon_orig_exit = con->exit; + con->exit = kgdboc_earlycon_deferred_exit; + } + +unlock: +console_unlock (); + +/* Non-zero means malformed option so we always return zero */ +return 0 ; +} + +early_param ("kgdboc_earlycon" , kgdboc_earlycon_init); +module_init (init_kgdboc);module_exit (exit_kgdboc);module_param_call (kgdboc, param_set_kgdboc_var, param_get_string, &kps,0644 );
include/linux/kgdb.h +4 -0
@@ -269,6 +269,9 @@ struct kgdb_arch {* @write_char: Pointer to a function that will write one char. * @flush: Pointer to a function that will flush any pending writes. * @init: Pointer to a function that will initialize the device. +* @deinit: Pointer to a function that will deinit the device. Implies that +* this I/O driver is temporary and expects to be replaced. Called when +* an I/O driver is replaced or explicitly unregistered. * @pre_exception: Pointer to a function that will do any prep work for * the I/O driver. * @post_exception: Pointer to a function that will do any cleanup work
@@ -282,6 +285,7 @@ struct kgdb_io {void (*write_char) (u8 );void (*flush) (void );int (*init) (void ); +void (*deinit) (void );void (*pre_exception) (void );void (*post_exception) (void );int is_console;
kernel/debug/debug_core.c +18 -4
@@ -1075,15 +1075,23 @@ EXPORT_SYMBOL_GPL(kgdb_schedule_breakpoint);*/ int kgdb_register_io_module (struct kgdb_io *new_dbg_io_ops) { +struct kgdb_io *old_dbg_io_ops;int err;spin_lock (&kgdb_registration_lock); -if (dbg_io_ops) { -spin_unlock (&kgdb_registration_lock); + old_dbg_io_ops = dbg_io_ops; +if (old_dbg_io_ops) { +if (!old_dbg_io_ops->deinit) { +spin_unlock (&kgdb_registration_lock); -pr_err ("Another I/O driver is already registered with KGDB\n" ); -return -EBUSY ; +pr_err ("KGDB I/O driver %s can't replace %s.\n" , + new_dbg_io_ops->name, old_dbg_io_ops->name); +return -EBUSY ; + } +pr_info ("Replacing I/O driver %s with %s\n" , + old_dbg_io_ops->name, new_dbg_io_ops->name); + old_dbg_io_ops->deinit (); }if (new_dbg_io_ops->init) {
@@ -1098,6 +1106,9 @@ int kgdb_register_io_module(struct kgdb_io *new_dbg_io_ops)spin_unlock (&kgdb_registration_lock); +if (old_dbg_io_ops) +return 0 ; +pr_info ("Registered I/O driver %s\n" , new_dbg_io_ops->name);/* Arm KGDB now. */
@@ -1134,6 +1145,9 @@ void kgdb_unregister_io_module(struct kgdb_io *old_dbg_io_ops)spin_unlock (&kgdb_registration_lock); +if (old_dbg_io_ops->deinit) + old_dbg_io_ops->deinit (); +pr_info ("Unregistered I/O driver %s, debugger disabled\n" , old_dbg_io_ops->name); }
Signature · 1 line
2.26.2.645.ge9eca65c58-goog
Douglas Anderson
reviewerPATCH v4 9/12 Documentation: kgdboc: Document new kgdboc_earlycon parameter
In reply to Douglas AndersonThe recent patch ("kgdboc: Add kgdboc_earlycon to support early kgdb using boot consoles") adds a new kernel command line parameter. Document it.
Note that the patch adding the feature does some comparing/contrasting of "kgdboc_earlycon" vs. the existing "ekgdboc". See that patch for more details, but briefly "ekgdboc" can be used _instead_ of "kgdboc" and just makes "kgdboc" do its normal initialization early (only works if your tty driver is already ready). The new "kgdboc_earlycon" works in combination with "kgdboc" and is backed by boot consoles.
---
Changes in v4:
- s/The the/The/
Changes in v3:
- Added example in kgdb.rst
- Removed unneeded sentence in kerenel-parameters doc.
- Renamed earlycon_kgdboc to kgdboc_earlycon.
- Suggest people use kgdboc_earlycon instead of ekgdboc.
Changes in v2: None
.../admin-guide/kernel-parameters.txt | 20 ++++++++++++++++ Documentation/dev-tools/kgdb.rst | 24 +++++++++++++++++++ 2 files changed, 44 insertions(+)
Documentation/admin-guide/kernel-parameters.txt +20 -0
@@ -1190,6 +1190,11 @@ This is designed to be used in conjunction with the boot argument: earlyprintk=vga + This parameter works in place of the kgdboc parameter + but can only be used if the backing tty is available + very early in the boot process. For early debugging + via a serial port see kgdboc_earlycon instead. + edd= [EDD] Format: {"off" | "on" | "skip[mbr]"}
@@ -2105,6 +2110,21 @@ kms, kbd format: kms,kbd kms, kbd and serial format: kms,kbd,<ser_dev>[,baud] + kgdboc_earlycon= [KGDB,HW] + If the boot console provides the ability to read + characters and can work in polling mode, you can use + this parameter to tell kgdb to use it as a backend + until the normal console is registered. Intended to + be used together with the kgdboc parameter which + specifies the normal console to transition to. + + The name of the early console should be specified + as the value of this parameter. Note that the name of + the early console might be different than the tty + name passed to kgdboc. It's OK to leave the value + blank and the first boot console that implements + read() will be picked. + kgdbwait [KGDB] Stop kernel execution and enter the kernel debugger at the earliest opportunity.
Documentation/dev-tools/kgdb.rst +24 -0
@@ -274,6 +274,30 @@ don't like this are to hack gdb to send the :kbd:`SysRq-G` for you as well as on the initial connect, or to use a debugger proxy that allows an unmodified gdb to do the debugging. +Kernel parameter: ``kgdboc_earlycon`` +------------------------------------- + +If you specify the kernel parameter ``kgdboc_earlycon`` and your serial +driver registers a boot console that supports polling (doesn't need +interrupts and implements a nonblocking read() function) kgdb will attempt +to work using the boot console until it can transition to the regular +tty driver specified by the ``kgdboc`` parameter. + +Normally there is only one boot console (especially that implements the +read() function) so just adding ``kgdboc_earlycon`` on its own is +sufficient to make this work. If you have more than one boot console you +can add the boot console's name to differentiate. Note that names that +are registered through the boot console layer and the tty layer are not +the same for the same port. + +For instance, on one board to be explicit you might do:: + + kgdboc_earlycon=qcom_geni kgdboc=ttyMSM0 + +If the only boot console on the device was "qcom_geni", you could simplify:: + + kgdboc_earlycon kgdboc=ttyMSM0 + Kernel parameter: ``kgdbwait`` ------------------------------
Signature · 1 line
2.26.2.645.ge9eca65c58-goog
Douglas Anderson
reviewerPATCH v4 10/12 serial: qcom_geni_serial: Support kgdboc_earlycon
In reply to Douglas AndersonImplement the read() function in the early console driver. With recent kgdb patches this allows you to use kgdb to debug fairly early into the system boot.
We only bother implementing this if polling is enabled since kgdb can't be enabled without that.
---
Changes in v4: None
Changes in v3:
- Renamed earlycon_kgdboc to kgdboc_earlycon.
- { ; } ==> { }
Changes in v2: None
drivers/tty/serial/qcom_geni_serial.c | 32 +++++++++++++++++++++++++++ 1 file changed, 32 insertions(+)
drivers/tty/serial/qcom_geni_serial.c +32 -0
@@ -1090,6 +1090,36 @@ static void qcom_geni_serial_earlycon_write(struct console *con,__qcom_geni_serial_console_write (&dev->port, s, n); } +#ifdef CONFIG_CONSOLE_POLL +static int qcom_geni_serial_earlycon_read (struct console *con, +char *s,unsigned int n) +{ +struct earlycon_device *dev = con->data; +struct uart_port *uport = &dev->port; +int num_read =0 ; +int ch; + +while (num_read < n) { + ch =qcom_geni_serial_get_char (uport); +if (ch ==NO_POLL_CHAR ) +break ; + s[num_read++] = ch; + } + +return num_read; +} + +static void __init qcom_geni_serial_enable_early_read (struct geni_se *se, +struct console *con) +{ +geni_se_setup_s_cmd (se,UART_START_READ ,0 ); + con->read = qcom_geni_serial_earlycon_read; +} +#else +static inline void qcom_geni_serial_enable_early_read (struct geni_se *se, +struct console *con) { } +#endif +static int __init qcom_geni_serial_earlycon_setup (struct earlycon_device *dev,const char *opt) {
@@ -1136,6 +1166,8 @@ static int __init qcom_geni_serial_earlycon_setup(struct earlycon_device *dev, dev->con->write = qcom_geni_serial_earlycon_write; dev->con->setup =NULL ; +qcom_geni_serial_enable_early_read (&se, dev->con); +return 0 ; } OF_EARLYCON_DECLARE(qcom_geni, "qcom,geni-debug-uart",
Signature · 1 line
2.26.2.645.ge9eca65c58-goog
Douglas Anderson
reviewerPATCH v4 11/12 serial: 8250_early: Support kgdboc_earlycon
In reply to Douglas AndersonImplement the read() function in the early console driver. With recent kgdb patches this allows you to use kgdb to debug fairly early into the system boot.
We only bother implementing this if polling is enabled since kgdb can't be enabled without that.
---
Changes in v4: None
Changes in v3:
- Renamed earlycon_kgdboc to kgdboc_earlycon.
Changes in v2: None
drivers/tty/serial/8250/8250_early.c | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+)
drivers/tty/serial/8250/8250_early.c +23 -0
@@ -109,6 +109,28 @@ static void early_serial8250_write(struct console *console,uart_console_write (port, s, count, serial_putc); } +#ifdef CONFIG_CONSOLE_POLL +static int early_serial8250_read (struct console *console, +char *s,unsigned int count) +{ +struct earlycon_device *device = console->data; +struct uart_port *port = &device->port; +unsigned int status; +int num_read =0 ; + +while (num_read < count) { + status =serial8250_early_in (port,UART_LSR ); +if (!(status &UART_LSR_DR )) +break ; + s[num_read++] =serial8250_early_in (port,UART_RX ); + } + +return num_read; +} +#else +#define early_serial8250_read NULL +#endif +static void __init init_port (struct earlycon_device *device) {struct uart_port *port = &device->port;
@@ -149,6 +171,7 @@ int __init early_serial8250_setup(struct earlycon_device *device,init_port (device); device->con->write = early_serial8250_write; + device->con->read = early_serial8250_read;return 0 ; }EARLYCON_DECLARE (uart8250, early_serial8250_setup);
Signature · 1 line
2.26.2.645.ge9eca65c58-goog
Douglas Anderson
reviewerPATCH v4 12/12 serial: amba-pl011: Support kgdboc_earlycon
In reply to Douglas AndersonFrom: Sumit Garg <[email protected]>
Implement the read() function in the early console driver. With recently added kgdboc_earlycon feature, this allows you to use kgdb to debug fairly early into the system boot.
We only bother implementing this if polling is enabled since kgdb can't be enabled without that.
---
Changes in v4: None
Changes in v3:
- ("serial: amba-pl011: Support kgdboc_earlycon") pulled into my v3.
- Renamed earlycon_kgdboc to kgdboc_earlycon.
Changes in v2: None
drivers/tty/serial/amba-pl011.c | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+)
drivers/tty/serial/amba-pl011.c +32 -0
@@ -2435,6 +2435,37 @@ static void pl011_early_write(struct console *con, const char *s, unsigned n)uart_console_write (&dev->port, s, n, pl011_putc); } +#ifdef CONFIG_CONSOLE_POLL +static int pl011_getc (struct uart_port *port) +{ +if (readl (port->membase + UART01x_FR) & UART01x_FR_RXFE) +return NO_POLL_CHAR ; + +if (port->iotype ==UPIO_MEM32 ) +return readl (port->membase + UART01x_DR); +else +return readb (port->membase + UART01x_DR); +} + +static int pl011_early_read (struct console *con,char *s,unsigned int n) +{ +struct earlycon_device *dev = con->data; +int ch, num_read =0 ; + +while (num_read < n) { + ch =pl011_getc (&dev->port); +if (ch ==NO_POLL_CHAR ) +break ; + + s[num_read++] = ch; + } + +return num_read; +} +#else +#define pl011_early_read NULL +#endif +/* * On non-ACPI systems, earlycon is enabled by specifying * "earlycon=pl011,<address>" on the kernel command line.
@@ -2454,6 +2485,7 @@ static int __init pl011_early_console_setup(struct earlycon_device *device,return -ENODEV ; device->con->write = pl011_early_write; + device->con->read = pl011_early_read;return 0 ; }
Signature · 1 line
2.26.2.645.ge9eca65c58-goog
Quoted 21 lines · Douglas Anderson
<snip>
My first attempt was to try to get the existing "ekgdboc" to work earlier. I tried that for a bit until I realized that it needed to work at the tty layer and I couldn't find any serial drivers that managed to register themselves to the tty layer super early at boot. The only documented use of "ekgdboc" is "ekgdboc=kbd" and that's a bit of a special snowflake. Trying to get my serial driver and all its dependencies to probe normally and register the tty driver super early at boot seemed like a bad way to go. In fact, all the complexity needed to do something like this is why the system already has a special concept of a "boot console" that lives only long enough to transition to the normal console.
<snip>
The devices I had for testing were:
- arm32: rk3288-veyron-jerry
- arm64: rk3399-gru-kevin
- arm64: qcom-sc7180-trogdor (not mainline yet)
Quoted 5 lines
These are the devices I tested this series on. I tried to test various combinations of enabling/disabling various options and I hopefully caught the corner cases, but I'd appreciate any extra testing people can do. Notably I didn't test on x86, but (I think) I didn't touch much there so I shouldn't have broken anything.
I have tested a slightly earlier version using qemu and will test this set before it moves forwards.
Quoted 7 lines
.../admin-guide/kernel-parameters.txt | 20 ++ Documentation/dev-tools/kgdb.rst | 24 ++ arch/arm64/Kconfig | 1 + arch/arm64/include/asm/debug-monitors.h | 2 + arch/arm64/kernel/debug-monitors.c | 2 +- arch/arm64/kernel/traps.c | 3 + arch/x86/Kconfig | 1 +
Quoted 8 lines
drivers/tty/serial/8250/8250_early.c | 23 ++ drivers/tty/serial/amba-pl011.c | 32 +++ drivers/tty/serial/kgdboc.c | 268 ++++++++++++++++-- drivers/tty/serial/qcom_geni_serial.c | 32 +++ include/linux/kgdb.h | 4 + kernel/debug/debug_core.c | 52 +++- lib/Kconfig.kgdb | 18 ++ 14 files changed, 436 insertions(+), 46 deletions(-)
Any thoughts on how best to land these changes?
AFAICT the arm64 and 8250/amba-pl011/qcom_geni_serial code could be applied independently of the kgdb changes (though we must keep changes to drivers/tty/serial/kgdboc alongside the kgdb changes).
I can hoover them up but I'd need a solid set of acks and I don't think we've got that yet.
I'd also be happy to ack where needed and let someone else pick it up (the other changes queued for kgdb this cycle are pretty small so we shouldn't see much conflict in kernel/debug/ ).
Daniel.
Doug Anderson
reviewerHi,
Quoted 49 lines · Daniel Thompson
Quoted 21 lines · Douglas Anderson
<snip>
My first attempt was to try to get the existing "ekgdboc" to work earlier. I tried that for a bit until I realized that it needed to work at the tty layer and I couldn't find any serial drivers that managed to register themselves to the tty layer super early at boot. The only documented use of "ekgdboc" is "ekgdboc=kbd" and that's a bit of a special snowflake. Trying to get my serial driver and all its dependencies to probe normally and register the tty driver super early at boot seemed like a bad way to go. In fact, all the complexity needed to do something like this is why the system already has a special concept of a "boot console" that lives only long enough to transition to the normal console.
<snip>
The devices I had for testing were:
- arm32: rk3288-veyron-jerry
- arm64: rk3399-gru-kevin
- arm64: qcom-sc7180-trogdor (not mainline yet)Quoted 5 lines
These are the devices I tested this series on. I tried to test various combinations of enabling/disabling various options and I hopefully caught the corner cases, but I'd appreciate any extra testing people can do. Notably I didn't test on x86, but (I think) I didn't touch much there so I shouldn't have broken anything.
I have tested a slightly earlier version using qemu and will test this set before it moves forwards.
Quoted 7 lines
.../admin-guide/kernel-parameters.txt | 20 ++ Documentation/dev-tools/kgdb.rst | 24 ++ arch/arm64/Kconfig | 1 + arch/arm64/include/asm/debug-monitors.h | 2 + arch/arm64/kernel/debug-monitors.c | 2 +- arch/arm64/kernel/traps.c | 3 + arch/x86/Kconfig | 1 +Quoted 8 lines
drivers/tty/serial/8250/8250_early.c | 23 ++ drivers/tty/serial/amba-pl011.c | 32 +++ drivers/tty/serial/kgdboc.c | 268 ++++++++++++++++-- drivers/tty/serial/qcom_geni_serial.c | 32 +++ include/linux/kgdb.h | 4 + kernel/debug/debug_core.c | 52 +++- lib/Kconfig.kgdb | 18 ++ 14 files changed, 436 insertions(+), 46 deletions(-)
Quoted 3 lines
Any thoughts on how best to land these changes?
AFAICT the arm64
I was hoping to get an Ack from Will or Catalin for my most recent arm64 patch [1] and then it could land in your tree. However, it wouldn't be the end of the world if that landed later. "kgdbwait" would be broken if you used it together with "kgdb_earlycon" but overall we'd still be in a better place than we were.
Quoted 2 lines
and 8250/amba-pl011/qcom_geni_serial code could be applied independently of the kgdb changes
Right, that would be OK. Nobody would actually be able to use "kgdb_earlycon" until those landed but there would be no problem with those two landing separately.
Quoted 5 lines
(though we must keep
changes todrivers/tty/serial/kgdbocalongside the kgdb changes).I can hoover them up but I'd need a solid set of acks and I don't think we've got that yet.
It would be nice for it to be explicit, but "get_maintainer" says that Greg KH is the maintainer of serial drivers. Git log confirms that he also has been the one landing changes to these files. Early-on he provided his Reviewed-by for the series as a whole, so he's aware of it and maybe would be fine w/ the serial changes landing through the kgdb tree?
Greg: is that correct?
Quoted 3 lines
I'd also be happy to ack where needed and let someone else pick it up (the other changes queued for kgdb this cycle are pretty small so we shouldn't see much conflict in
kernel/debug/).
It feels to me that the kgdb tree is the best destination for all these patches if possible.
[1] https://lore.kernel.org/r/20200513160501.1.I0b5edf030cc6ebef6ab4829f8867cdaea42485d8@changeid
-Doug
Greg Kroah-Hartman
maintainerQuoted 6 lines · Doug Anderson
Quoted 5 lines
(though we must keep
changes todrivers/tty/serial/kgdbocalongside the kgdb changes).I can hoover them up but I'd need a solid set of acks and I don't think we've got that yet.
Quoted 8 lines
It would be nice for it to be explicit, but "
get_maintainer" says that Greg KH is the maintainer of serial drivers. Git log confirms that he also has been the one landing changes to these files. Early-on he provided his Reviewed-by for the series as a whole, so he's aware of it and maybe would be fine w/ the serial changes landing through the kgdb tree?Greg: is that correct?
I have no objection for all of these to go through any other tree that wants to take them :)
But if you want me to take them in the serial tree, to make it easier for you or any other serial driver issues, I will be glad to do that, just send them my way. It's your call.
thanks,
greg k-h
Quoted 14 lines · Greg Kroah-Hartman
Quoted 13 lines · Doug Anderson
Quoted 5 lines
(though we must keep
changes todrivers/tty/serial/kgdbocalongside the kgdb changes).I can hoover them up but I'd need a solid set of acks and I don't think we've got that yet.
It would be nice for it to be explicit, but "
get_maintainer" says that Greg KH is the maintainer of serial drivers. Git log confirms that he also has been the one landing changes to these files. Early-on he provided his Reviewed-by for the series as a whole, so he's aware of it and maybe would be fine w/ the serial changes landing through the kgdb tree?
Quoted 8 lines
Quoted 1 line
Greg: is that correct?
I have no objection for all of these to go through any other tree that wants to take them :)
But if you want me to take them in the serial tree, to make it easier for you or any other serial driver issues, I will be glad to do that, just send them my way. It's your call.
Thanks. I've taken then via my tree.
Daniel.
Quoted 12 lines · Douglas Anderson
This whole pile of patches was motivated by me trying to get kgdb to work properly on a platform where my serial driver ended up being hit by the -EPROBE_DEFER virus (it wasn't practicing social distancing from other drivers). Specifically my serial driver's parent device depended on a resource that wasn't available when its probe was first called. It returned -EPROBE_DEFER which meant that when "kgdboc" tried to run its setup the serial driver wasn't there. Unfortunately "kgdboc" never tried again, so that meant that kgdb was disabled until I manually enalbed it via sysfs.
<snip>
Quoted 7 lines
This series (and my comments / documentation / commit messages) are now long enough that my eyes glaze over when I try to read it all over to double-check. I've nontheless tried to double-check it, but I'm pretty sure I did something stupid. Thank you ahead of time for pointing it out to me so I can fix it in v5. If somehow I managed to not do anything stupid (really?) then thank you for double-checking me anyway.
Applied (minus the arm64 specific stuff), should be in the next linux-next.
Daniel.