Received: by 2002:a25:23cc:0:0:0:0:0 with SMTP id j195csp1032470ybj; Thu, 7 May 2020 13:11:15 -0700 (PDT) X-Google-Smtp-Source: APiQypIQATJz8b1/oxpOXmnTkvKc5LvjEddiDHWrJON/fFs1zz1Lr0Hpxiy0mVR3xemye0XXj3dC X-Received: by 2002:a17:906:328f:: with SMTP id 15mr14602800ejw.33.1588882275612; Thu, 07 May 2020 13:11:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588882275; cv=none; d=google.com; s=arc-20160816; b=eH7xb5ryzuHyftC4/89/AF1SsCysVnYYDsXOKt63UWkecvLoJoMORhva0ZQvwX443s Ts162sVuC4srXQHyCutOew7BO7RbIYa0C0fSdgFyUOllblvk+H1qcM4rgLPTfZycvhns d9gIOT9CY/iZ7fqoiQVXs5FhFq6GzPctrn5i7YIf6XLVDBeaojGVxlcu2QKOJMUzrHXH N7yHp0jdqg++Q9dhwNT5Cu0bM5NtbxzjDk76McGv5INzKjBG0bzYu8CdFh0FwpHoykSL wN5d2hrB6CrbeMJU9F7bgMW2dvI2vJug4QQnkukJTifbiRkpHdh+Ke/tyMc090ec4xqp OcEQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=JZVfMDRlaZxQ6qpzAMsiTzN4YCAYznWKH75NGk0mLe0=; b=RJ2Z7bapTtNATf3mI9Nqg2AovrnZOwTVudEb3R+JvHyEt7zr55dUrh7FBz1Tli6+vF JZZqtQJ9azDgmNrlOPAoU796JeEmsWtHJD5smxFqeXGRTikycb5uzHCaIUdzJaw2moRY vTvYtgZaCLlNv8tNNha3AUotn/HxgobFSdYFsD9EuErg0UYOTFSlrV5mfHlSWgF/yE84 uTdzoF+DgC89Drj8klTcxmnT6nrXXcCNN6yHq3KbpIG22c4587DYwlXNd2a4E/pMrNmx uvZi/IuXlRVZUGVr/iPoROZNqV1+1UgdnhMTB+Z80jfk2YYBDt6n+Zl1BMIcSw+tqAMH e96g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=m5ylYMv8; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id fi25si3939534ejb.25.2020.05.07.13.10.52; Thu, 07 May 2020 13:11:15 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=m5ylYMv8; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728697AbgEGUJT (ORCPT + 99 others); Thu, 7 May 2020 16:09:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45858 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1728611AbgEGUJN (ORCPT ); Thu, 7 May 2020 16:09:13 -0400 Received: from mail-pl1-x641.google.com (mail-pl1-x641.google.com [IPv6:2607:f8b0:4864:20::641]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E5326C05BD0B for ; Thu, 7 May 2020 13:09:12 -0700 (PDT) Received: by mail-pl1-x641.google.com with SMTP id t16so2515155plo.7 for ; Thu, 07 May 2020 13:09:12 -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:in-reply-to:references :mime-version:content-transfer-encoding; bh=JZVfMDRlaZxQ6qpzAMsiTzN4YCAYznWKH75NGk0mLe0=; b=m5ylYMv87Zesz+z8ZAznR4kWc9TIjqXmxiLRRY8QyOpCZOwt00FTXHCWaihQzLwGTB /kjZ0p7FzdVuwoHXJtcPF3yVROz9sUTpYmZCbApuKUmPUpqHuEyGNlO3TyZwioK9zYWZ M773j7obrswcIlQPjJ858TSOKYbtG52zYMVnA= 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:in-reply-to :references:mime-version:content-transfer-encoding; bh=JZVfMDRlaZxQ6qpzAMsiTzN4YCAYznWKH75NGk0mLe0=; b=fjOMVjDx5BKVr+k62RYvwmCo78ywIbT1cD+gX/+PGdAn9Fb+ukafcy/vWyQRLMMbeL 7gHiZS6iXDL47xEYz6Vjk64v36/H9GeKYsWVyKTvrVGMZk1TsFZa6TeXV7ibhVGVk9Aw VeO9m4tbsuiPoy5rOMqpKgs0hP7YrgNoI5jIbt2NiiCpPx3m0IJbXCSAyuBxqrqPckQJ ojE9tnXXGU4KH7o1qF6vaDupH11EJEN4FIXiMVQK7vKaTLm9B0AGyVZuuTX8jqCcz4Fa s5fOdsVQxBI5p82GlXAtxdXEm4GY2eXAi+W2ZEofJTX3O9nt33O92X6eBotOwf8OUNLX nxSQ== X-Gm-Message-State: AGi0PuZyhc+lBW3ItvtwxkRJwUPdBoYewuqzZ/pC+1GaeIssSq3Obu3k 1vbHKZ8aheyAa3o2FRayVmXqBg== X-Received: by 2002:a17:902:c193:: with SMTP id d19mr15373854pld.60.1588882152281; Thu, 07 May 2020 13:09:12 -0700 (PDT) Received: from tictac2.mtv.corp.google.com ([2620:15c:202:1:24fa:e766:52c9:e3b2]) by smtp.gmail.com with ESMTPSA id d203sm5547601pfd.79.2020.05.07.13.09.10 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 07 May 2020 13:09:11 -0700 (PDT) From: Douglas Anderson To: jason.wessel@windriver.com, daniel.thompson@linaro.org, gregkh@linuxfoundation.org Cc: corbet@lwn.net, frowand.list@gmail.com, bjorn.andersson@linaro.org, linux-serial@vger.kernel.org, mingo@redhat.com, hpa@zytor.com, jslaby@suse.com, kgdb-bugreport@lists.sourceforge.net, sumit.garg@linaro.org, will@kernel.org, tglx@linutronix.de, agross@kernel.org, catalin.marinas@arm.com, bp@alien8.de, Douglas Anderson , Andrew Morton , Juergen Gross , Mauro Carvalho Chehab , Pawan Gupta , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v4 09/12] Documentation: kgdboc: Document new kgdboc_earlycon parameter Date: Thu, 7 May 2020 13:08:47 -0700 Message-Id: <20200507130644.v4.9.I7d5eb42c6180c831d47aef1af44d0b8be3fac559@changeid> X-Mailer: git-send-email 2.26.2.645.ge9eca65c58-goog In-Reply-To: <20200507200850.60646-1-dianders@chromium.org> References: <20200507200850.60646-1-dianders@chromium.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The 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. Signed-off-by: Douglas Anderson Reviewed-by: Greg Kroah-Hartman Reviewed-by: Daniel Thompson --- 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(+) diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt index 7bc83f3d9bdf..2cbde9ea476d 100644 --- a/Documentation/admin-guide/kernel-parameters.txt +++ b/Documentation/admin-guide/kernel-parameters.txt @@ -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,[,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. diff --git a/Documentation/dev-tools/kgdb.rst b/Documentation/dev-tools/kgdb.rst index d38be58f872a..61293f40bc6e 100644 --- a/Documentation/dev-tools/kgdb.rst +++ b/Documentation/dev-tools/kgdb.rst @@ -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`` ------------------------------ -- 2.26.2.645.ge9eca65c58-goog