From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,USER_AGENT_SANE_2 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 45BEEC83000 for ; Thu, 30 Apr 2020 00:58:04 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 299582083B for ; Thu, 30 Apr 2020 00:58:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726309AbgD3A6D (ORCPT ); Wed, 29 Apr 2020 20:58:03 -0400 Received: from mail.kernel.org ([198.145.29.99]:58822 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726279AbgD3A6D (ORCPT ); Wed, 29 Apr 2020 20:58:03 -0400 Received: from oasis.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id CF92E20787; Thu, 30 Apr 2020 00:58:02 +0000 (UTC) Date: Wed, 29 Apr 2020 20:58:01 -0400 From: Steven Rostedt To: Stephen Kitt Cc: Jonathan Corbet , Mauro Carvalho Chehab , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 1/2] docs: sysctl/kernel: document ftrace entries Message-ID: <20200429205801.5ce95ab3@oasis.local.home> In-Reply-To: <20200429205757.8677-1-steve@sk2.org> References: <20200429205757.8677-1-steve@sk2.org> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-doc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org On Wed, 29 Apr 2020 22:57:56 +0200 Stephen Kitt wrote: > Based on the ftrace documentation, the tp_printk boot parameter > documentation, and the implementation in kernel/trace/trace.c. > > Signed-off-by: Stephen Kitt > --- > Changes since v2: > - spelling and grammar fixes in ftrace_dump_on_oops ("outputing it" > -> "outputting them") > - "and::" in a single line in tracepoint_printk I didn't re-read or compare this patch with v1, but if the only changes were the above: Acked-by: Steven Rostedt (VMware) -- Steve > > Documentation/admin-guide/sysctl/kernel.rst | 48 +++++++++++++++++++++ > 1 file changed, 48 insertions(+) > > diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst > index 82bfd5892663..b1ad4c86274d 100644 > --- a/Documentation/admin-guide/sysctl/kernel.rst > +++ b/Documentation/admin-guide/sysctl/kernel.rst > @@ -265,6 +265,27 @@ domain names are in general different. For a detailed discussion > see the ``hostname(1)`` man page. > > > +ftrace_dump_on_oops > +=================== > + > +Determines whether ``ftrace_dump()`` should be called on an oops (or > +kernel panic). This will output the contents of the ftrace buffers to > +the console. This is very useful for capturing traces that lead to > +crashes and outputting them to a serial console. > + > += =================================================== > +0 Disabled (default). > +1 Dump buffers of all CPUs. > +2 Dump the buffer of the CPU that triggered the oops. > += =================================================== > + > + > +ftrace_enabled, stack_tracer_enabled > +==================================== > + > +See :doc:`/trace/ftrace`. > + > + > hardlockup_all_cpu_backtrace > ============================ > > @@ -1191,6 +1212,33 @@ If a value outside of this range is written to ``threads-max`` an > ``EINVAL`` error occurs. > > > +traceoff_on_warning > +=================== > + > +When set, disables tracing (see :doc:`/trace/ftrace`) when a > +``WARN()`` is hit. > + > + > +tracepoint_printk > +================= > + > +When tracepoints are sent to printk() (enabled by the ``tp_printk`` > +boot parameter), this entry provides runtime control:: > + > + echo 0 > /proc/sys/kernel/tracepoint_printk > + > +will stop tracepoints from being sent to printk(), and:: > + > + echo 1 > /proc/sys/kernel/tracepoint_printk > + > +will send them to printk() again. > + > +This only works if the kernel was booted with ``tp_printk`` enabled. > + > +See :doc:`/admin-guide/kernel-parameters` and > +:doc:`/trace/boottime-trace`. > + > + > unknown_nmi_panic > ================= >