From: Steven Rostedt <rostedt@goodmis.org>
To: "Huang\, Ying" <ying.huang@intel.com>
Cc: Mengyang Liu <mengyang.liu@intel.com>, "Brandt\,
Todd E" <todd.e.brandt@intel.com>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Is it possible to use ftrace to measure secondary CPU bootup time
Date: Mon, 24 Jul 2017 05:17:02 -0400 [thread overview]
Message-ID: <20170724051702.5a0a4ec8@vmware.local.home> (raw)
In-Reply-To: <874lu2fkv4.fsf@yhuang-dev.intel.com>
On Mon, 24 Jul 2017 13:46:07 +0800
"Huang\, Ying" <ying.huang@intel.com> wrote:
> Hi, Steven,
>
> We are working on parallelizing secondary CPU bootup. So we need to
> measure the bootup time of secondary CPU, that is, measure time spent in
> smp_init() and its callees. But we found that ftrace now doesn't
> support measure time spent in smp_init() because it is called too early
> (before core_initcall()?). So, do you think it is possible to use
> ftrace to measure secondary CPU bootup time?
One could trace with function tracing that early, but that wont give
you the timings you are looking for. The best it probably could do is
to look at the function timestamps of what is called after smp_init.
That is, trace smp_init() and sched_init_smp() and take the difference.
Function graph tracing (which is what you are probably looking for) is
much more heavy weight than function tracing. It requires some setup
that isn't ready that early. Although, I'm sure I can work to get it
there, but it's not trivial.
-- Steve
next prev parent reply other threads:[~2017-07-24 9:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 5:46 Huang, Ying
2017-07-24 9:17 ` Steven Rostedt [this message]
2017-07-24 21:40 ` Brandt, Todd E
2017-07-26 21:20 ` Steven Rostedt
2017-07-25 0:34 ` Huang, Ying
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=20170724051702.5a0a4ec8@vmware.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mengyang.liu@intel.com \
--cc=todd.e.brandt@intel.com \
--cc=ying.huang@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
all inboxes | Powered by JetHome®