From patchwork Tue Apr 28 21:13:40 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Doug Anderson X-Patchwork-Id: 11515643 Return-Path: Received: from mail.kernel.org (pdx-korg-mail-1.web.codeaurora.org [172.30.200.123]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id 82F6F92C for ; Tue, 28 Apr 2020 21:14:32 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 5C3B62076A for ; Tue, 28 Apr 2020 21:14:32 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="LVmjugUr"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="UNNXZ0gc" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 5C3B62076A Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=chromium.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+patchwork-linux-arm=patchwork.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:Message-Id:Date:Subject:To :From:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References: List-Owner; bh=6AYIbmIlzp0JChT0VfzyQsHEGFzpOmtJpqzdB8KF9UE=; b=LVmjugUrausutU fp1rfflWVrJgU/fBb9Pxy21JsFgu/U2VwdkJOuI2qt8lupwDxHZpd2nCpKLhyhGlM1ofnZuO1wg5z jEUyYmr3OIRfyoohAx8I+OB87bfj8049JFZbosHM7SHx0sPQ7uctR4opiJFjG94PmfRhG9hyhogOk /Z5QddherfJC669yJBLQy3V403QpaV46SvBDfNlV60k3A/lVteNyQnuRJdBjIuR6jVNiaEpQW4GIE 3dsZTiO0WKrljEx9LZ/kN/uvv7n1uvNzFbyPTyy5X/TGINfHS2iMtfUgh/H+GcfIGqZiIk7vW31F9 NtTxk+INcCDqplWYIQPQ==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1jTXYf-00066v-3u; Tue, 28 Apr 2020 21:14:25 +0000 Received: from mail-pj1-x1043.google.com ([2607:f8b0:4864:20::1043]) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1jTXYb-00065r-M9 for linux-arm-kernel@lists.infradead.org; Tue, 28 Apr 2020 21:14:23 +0000 Received: by mail-pj1-x1043.google.com with SMTP id a5so57942pjh.2 for ; Tue, 28 Apr 2020 14:14:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=blBX9PWhrLwlRC4CxObQ1qK+sOW74s4G2bfD1JGu8J0=; b=UNNXZ0gcnR3k6hJj/LbVp66fJcTUI1AFvWnj3RHMoXFYmyCcp6PtCAYQY6fvgKQeJD MNV2wxAxPwLdM2hLs+qKupu4j9AUnqtqg77PSykw/jl+HCbCHt+4x9VIpHELo/PYeprO ilL6JtVgwda3tXbtK2W1ejaJ71UjYuT29uXvM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=blBX9PWhrLwlRC4CxObQ1qK+sOW74s4G2bfD1JGu8J0=; b=L927gN8uUMaJTU9plP5kt6x7XQM3B+0GAVX10TSvEsUiZEPPWSVa8Xhsc9b/FXnu+X DWqxFhwSjjh/Nlqz4eTc8cO6PhlGa4nx3eirf39HsiTDLR1tYjQM5Ed0TUY8+3uiZuEu PGDzV0s7fJi/2/muDhxBZurxJOBn9Wu9NajFT7NqghvxPpjWgJq6+Ao3S+TZfagOt3ul 3xnDUeZKnDLpTd0BO/ISMoXigz9RYY7qxIps/fLs+NpcUssQjkwRioJO48p8E1ZcnNJj e0UBEBMdWXqAigQfhz5IqC68ZmVu2ptt7u/S4B60a53kG0IkIxCB4f9mFAOEgkS0SCAo 7iGw== X-Gm-Message-State: AGi0PuZq+VVXWY/nigED3Oydg0GglzC/8sCmTAd8OrIezO8I+Aq5wA24 GoeFW9ZbKvIvAZTnZx7AVaEzUg== X-Google-Smtp-Source: APiQypLBYIwFGtYJq3pkWPIKkLwZi7SFfBVlMgfwE6B5z2rF+bbbLHTii8gKjfoQdnIZvUKuTl6BCA== X-Received: by 2002:a17:90a:718c:: with SMTP id i12mr7485056pjk.58.1588108458221; Tue, 28 Apr 2020 14:14:18 -0700 (PDT) Received: from tictac2.mtv.corp.google.com ([2620:15c:202:1:24fa:e766:52c9:e3b2]) by smtp.gmail.com with ESMTPSA id 18sm2988202pjf.30.2020.04.28.14.14.16 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 28 Apr 2020 14:14:17 -0700 (PDT) From: Douglas Anderson To: jason.wessel@windriver.com, daniel.thompson@linaro.org, gregkh@linuxfoundation.org Subject: [PATCH v3 00/11] kgdb: Support late serial drivers; enable early debug w/ boot consoles Date: Tue, 28 Apr 2020 14:13:40 -0700 Message-Id: <20200428211351.85055-1-dianders@chromium.org> X-Mailer: git-send-email 2.26.2.303.gf8c07b1a785-goog MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200428_141421_747975_5A31FA0F X-CRM114-Status: GOOD ( 27.56 ) X-Spam-Score: -0.2 (/) X-Spam-Report: SpamAssassin version 3.4.4 on bombadil.infradead.org summary: Content analysis details: (-0.2 points) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at https://www.dnswl.org/, no trust [2607:f8b0:4864:20:0:0:0:1043 listed in] [list.dnswl.org] 0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_EF Message has a valid DKIM or DK signature from envelope-from domain -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature -0.0 DKIMWL_WL_HIGH DKIMwl.org - Whitelisted High sender X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Mark Rutland , linux-doc@vger.kernel.org, kgdb-bugreport@lists.sourceforge.net, bjorn.andersson@linaro.org, hpa@zytor.com, Mauro Carvalho Chehab , frowand.list@gmail.com, corbet@lwn.net, will@kernel.org, x86@kernel.org, Russell King , Krzysztof Kozlowski , jinho lim , agross@kernel.org, Pawan Gupta , linux-arm-kernel@lists.infradead.org, linux-serial@vger.kernel.org, catalin.marinas@arm.com, Dave Martin , Masami Hiramatsu , linux-arm-msm@vger.kernel.org, jslaby@suse.com, Alexios Zavras , bp@alien8.de, tglx@linutronix.de, mingo@redhat.com, Allison Randal , Juergen Gross , sumit.garg@linaro.org, Douglas Anderson , linux-kernel@vger.kernel.org, James Morse , "Eric W. Biederman" , Andrew Morton Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+patchwork-linux-arm=patchwork.kernel.org@lists.infradead.org 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 v4. 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 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 (10): 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: 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 | 266 ++++++++++++++++-- drivers/tty/serial/qcom_geni_serial.c | 32 +++ include/linux/kgdb.h | 4 + kernel/debug/debug_core.c | 53 +++- lib/Kconfig.kgdb | 18 ++ 14 files changed, 437 insertions(+), 44 deletions(-)