From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Rostedt Subject: Re: [RFC PATCH v2 0/1] of: easier debugging for node life cycle issues Date: Thu, 1 Feb 2018 12:10:15 -0500 Message-ID: <20180201121015.72fd242c@gandalf.local.home> References: <20180121143117.19805-1-wsa+renesas@sang-engineering.com> <00fc90ee-de26-f819-9c81-27d06918564d@gmail.com> <20180125060330.781667e9@vmware.local.home> <20180125231443.44yy65ztr6exaam7@ninjato> <4b373579-7a86-6883-2624-12a5408bb49b@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4b373579-7a86-6883-2624-12a5408bb49b@gmail.com> Sender: linux-renesas-soc-owner@vger.kernel.org To: Frank Rowand Cc: Wolfram Sang , 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 List-Id: devicetree@vger.kernel.org On Thu, 25 Jan 2018 16:46:06 -0800 Frank Rowand wrote: > The point is that using ftrace means there are use cases for the > debug information where the information will not be available. Note, this email came out when I was traveling. I'm now looking at the code and trace events are enabled right after rcu_init() in init/main.c. The early_initcall() enables syscall events(), as they are not available earlier. -- Steve