Re: [PATCH] ftrace: add ftrace_graph_max_depth kernel parameter

On Thu, 02 Mar 2017 17:35:31 -0800 Todd Brandt wrote: > > I could toy with the idea, implement it, and see what breaks. > If it was possible that would be great. The reason I ask is because I've > implemented a tool called analyze_boot which I intend to upgrade

Re: [PATCH] ftrace: add ftrace_graph_max_depth kernel parameter

On Thu, 02 Mar 2017 17:35:31 -0800 Todd Brandt wrote: > > I could toy with the idea, implement it, and see what breaks. > If it was possible that would be great. The reason I ask is because I've > implemented a tool called analyze_boot which I intend to upgrade to use > early callgraph trace

Re: [PATCH] ftrace: add ftrace_graph_max_depth kernel parameter

On Thu, 02 Mar 2017 16:54:57 -0800 Todd Brandt wrote: > BTW I had one other question for you, is it possible to move the ftrace > module's initialization further up the queue? ATM it initializes at > about 600ms into boot, which is fine since most of the

Re: [PATCH] ftrace: add ftrace_graph_max_depth kernel parameter

On Thu, 02 Mar 2017 16:54:57 -0800 Todd Brandt wrote: > BTW I had one other question for you, is it possible to move the ftrace > module's initialization further up the queue? ATM it initializes at > about 600ms into boot, which is fine since most of the performance > issues are happening at

Re: [PATCH] ftrace: add ftrace_graph_max_depth kernel parameter

On Thu, 2 Mar 2017 16:12:15 -0800 Todd Brandt wrote: > Early trace callgraphs can be extremely large on systems with > several seconds of boot time. The max_depth parameter limits how > deep the graph trace goes and reduces the output size. This > parameter is the

Re: [PATCH] ftrace: add ftrace_graph_max_depth kernel parameter

On Thu, 2 Mar 2017 16:12:15 -0800 Todd Brandt wrote: > Early trace callgraphs can be extremely large on systems with > several seconds of boot time. The max_depth parameter limits how > deep the graph trace goes and reduces the output size. This > parameter is the same as the max_graph_depth

Re: [PATCH] ftrace: add ftrace_graph_max_depth kernel parameter

On Thu, 2017-03-02 at 20:09 -0500, Steven Rostedt wrote: > On Thu, 02 Mar 2017 16:54:57 -0800 > Todd Brandt wrote: > > > > BTW I had one other question for you, is it possible to move the ftrace > > module's initialization further up the queue? ATM it initializes

Re: [PATCH] ftrace: add ftrace_graph_max_depth kernel parameter

On Thu, 2017-03-02 at 20:09 -0500, Steven Rostedt wrote: > On Thu, 02 Mar 2017 16:54:57 -0800 > Todd Brandt wrote: > > > > BTW I had one other question for you, is it possible to move the ftrace > > module's initialization further up the queue? ATM it initializes at > > about 600ms into boot,

Re: [PATCH] ftrace: add ftrace_graph_max_depth kernel parameter

On Thu, 2017-03-02 at 19:39 -0500, Steven Rostedt wrote: > On Thu, 2 Mar 2017 19:38:27 -0500 > Steven Rostedt wrote: > > > On Thu, 2 Mar 2017 16:12:15 -0800 > > Todd Brandt wrote: > > > > > Early trace callgraphs can be extremely large on

Re: [PATCH] ftrace: add ftrace_graph_max_depth kernel parameter

On Thu, 2017-03-02 at 19:39 -0500, Steven Rostedt wrote: > On Thu, 2 Mar 2017 19:38:27 -0500 > Steven Rostedt wrote: > > > On Thu, 2 Mar 2017 16:12:15 -0800 > > Todd Brandt wrote: > > > > > Early trace callgraphs can be extremely large on systems with > > > several seconds of boot time. The

Re: [PATCH] ftrace: add ftrace_graph_max_depth kernel parameter

On Thu, 2 Mar 2017 19:38:27 -0500 Steven Rostedt wrote: > On Thu, 2 Mar 2017 16:12:15 -0800 > Todd Brandt wrote: > > > Early trace callgraphs can be extremely large on systems with > > several seconds of boot time. The max_depth parameter

Re: [PATCH] ftrace: add ftrace_graph_max_depth kernel parameter

On Thu, 2 Mar 2017 19:38:27 -0500 Steven Rostedt wrote: > On Thu, 2 Mar 2017 16:12:15 -0800 > Todd Brandt wrote: > > > Early trace callgraphs can be extremely large on systems with > > several seconds of boot time. The max_depth parameter limits how > > deep the graph trace goes and reduces

[PATCH] ftrace: add ftrace_graph_max_depth kernel parameter

Early trace callgraphs can be extremely large on systems with several seconds of boot time. The max_depth parameter limits how deep the graph trace goes and reduces the output size. This parameter is the same as the max_graph_depth file in debugfs. Signed-off-by: Todd Brandt

[PATCH] ftrace: add ftrace_graph_max_depth kernel parameter

Early trace callgraphs can be extremely large on systems with several seconds of boot time. The max_depth parameter limits how deep the graph trace goes and reduces the output size. This parameter is the same as the max_graph_depth file in debugfs. Signed-off-by: Todd Brandt ---