From: Steven Rostedt <rostedt@goodmis.org>
To: Todd Brandt <todd.e.brandt@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, todd.e.brandt@intel.com,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] ftrace: add ftrace_graph_max_depth kernel parameter
Date: Fri, 3 Mar 2017 09:31:23 -0500 [thread overview]
Message-ID: <20170303093123.5fa413bf@gandalf.local.home> (raw)
In-Reply-To: <1488504931.7212.41.camel@linux.intel.com>
On Thu, 02 Mar 2017 17:35:31 -0800
Todd Brandt <todd.e.brandt@linux.intel.com> 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 (it just uses initcall_debug now):
>
> https://marc.info/?l=linux-pm&m=148667508500967&w=2
>
> I'll have it do the same thing for boot that analyze_suspend does for
> suspend/resume: display the callgraphs for each initcall instance in
> html. The max_graph_depth param is necessary to keep the html outputs
> manageable. Most laptop/desktop machines running standard linux seem to
> take at least 5 seconds for boot, but we've got some servers optimized
> to boot in less than a second (which means I'd only be able to trace
> half of the boot timeline or less). The more coverage I can get the
> better.
>
> P.S. I submitted the analyze_boot tool on the pm list but Raphael didn't
> think it would fit in the PM tree. Would you be willing to accept this
> script? (I can resubmit but nothing's changed since the RESEND).
That may be something to ask Andrew about. He's sorta the one to dump
changes to that don't seem to fit anywhere else.
-- Steve
prev parent reply other threads:[~2017-03-03 15:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 0:12 [PATCH] ftrace: add ftrace_graph_max_depth kernel parameter Todd Brandt
2017-03-03 0:38 ` Steven Rostedt
2017-03-03 0:39 ` Steven Rostedt
2017-03-03 0:54 ` Todd Brandt
2017-03-03 1:09 ` Steven Rostedt
2017-03-03 1:35 ` Todd Brandt
2017-03-03 14:31 ` Steven Rostedt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170303093123.5fa413bf@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=todd.e.brandt@intel.com \
--cc=todd.e.brandt@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).