From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751588AbeAYLDl (ORCPT ); Thu, 25 Jan 2018 06:03:41 -0500 Received: from mail.kernel.org ([198.145.29.99]:41646 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751188AbeAYLDj (ORCPT ); Thu, 25 Jan 2018 06:03:39 -0500 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6AA5C21778 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=goodmis.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=rostedt@goodmis.org Date: Thu, 25 Jan 2018 06:03:30 -0500 From: Steven Rostedt To: Frank Rowand Cc: Wolfram Sang , devicetree@vger.kernel.org, Tyrel Datwyler , Geert Uytterhoeven , linux-renesas-soc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, Rob Herring , linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH v2 0/1] of: easier debugging for node life cycle issues Message-ID: <20180125060330.781667e9@vmware.local.home> In-Reply-To: <00fc90ee-de26-f819-9c81-27d06918564d@gmail.com> References: <20180121143117.19805-1-wsa+renesas@sang-engineering.com> <00fc90ee-de26-f819-9c81-27d06918564d@gmail.com> X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 24 Jan 2018 22:55:13 -0800 Frank Rowand wrote: > Hi Steve, > > Off the top of your head, can you tell me know early in the boot > process a trace_event can be called and successfully provide the > data to someone trying to debug early boot issues? The trace events are enabled by early_initcall(). > > Also, way back when version 1 of this patch was being discussed, > a question about stacktrace triggers: > > >>> # echo stacktrace > /sys/kernel/debug/tracing/trace_options > >>> # cat trace | grep -A6 "/pci@800000020000018" > >> > >> Just to let you know that there is now stacktrace event triggers, where > >> you don't need to stacktrace all events, you can pick and choose. And > >> even filter the stack trace on specific fields of the event. > > > > This is great, and I did figure that out this afternoon. One thing I was > > still trying to determine though was whether its possible to set these > > triggers at boot? As far as I could tell I'm still limited to > > "trace_options=stacktrace" as a kernel boot parameter to get the stack > > for event tracepoints. > > No not yet. But I'll add that to the todo list. > > Thanks, > > -- Steve > > Is this still on your todo list, or is it now available? Still on the todo list. As someone once said, there really is no todo list, but just work on the stuff that people are yelling the loudest about. Yell louder, and it will get done quicker ;-) -- Steve