[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180201121015.72fd242c@gandalf.local.home>
Date: Thu, 1 Feb 2018 12:10:15 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Frank Rowand <frowand.list@...il.com>
Cc: Wolfram Sang <wsa@...-dreams.de>,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
devicetree@...r.kernel.org,
Tyrel Datwyler <tyreld@...ux.vnet.ibm.com>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
linux-renesas-soc@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
Rob Herring <robh+dt@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH v2 0/1] of: easier debugging for node life cycle
issues
On Thu, 25 Jan 2018 16:46:06 -0800
Frank Rowand <frowand.list@...il.com> 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
Powered by blists - more mailing lists