linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Itai Handler <itai.handler@gmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: aarch64 boot time increases with rt
Date: Tue, 14 Jul 2020 10:34:43 -0400	[thread overview]
Message-ID: <20200714103443.31895064@oasis.local.home> (raw)
In-Reply-To: <CAFpOueRmBfzhPFb-q_pB1xpCQq4Cuo7rCCsc2eUPsGdaei-+3A@mail.gmail.com>

On Tue, 14 Jul 2020 15:18:01 +0300
Itai Handler <itai.handler@gmail.com> wrote:

> I tried "ftrace=function_graph ftrace_graph_filter=workqueue_prepare_cpu",
> however, the trace appears to be empty.
> The function workqueue_prepare_cpu is not defined inline nor notrace.
> 
> Please see log below:
> # mount -t debugfs none /sys/kernel/debug
> # cd /sys/kernel/debug/tracing/
> # cat trace
> # tracer: function_graph
> #
> # CPU  DURATION                  FUNCTION CALLS
> # |     |   |                     |   |   |   |
> # cat set_graph_function
> workqueue_prepare_cpu
> # cat tracing_on
> 1
> 
> Do you have any idea why it's empty?

Hmm, does the place in question happen before ftrace is initialized?

That is, where do you see the message that has something like this:

 ftrace: allocating 41803 entries in 164 pages
 ftrace: allocated 164 pages with 3 groups

-- Steve

  reply	other threads:[~2020-07-14 14:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13 14:56 aarch64 boot time increases with rt Itai Handler
2020-07-14  1:20 ` Steven Rostedt
2020-07-14 12:18   ` Itai Handler
2020-07-14 14:34     ` Steven Rostedt [this message]
2020-07-15 19:36     ` Steven Rostedt
2020-07-16 13:04       ` Itai Handler

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=20200714103443.31895064@oasis.local.home \
    --to=rostedt@goodmis.org \
    --cc=itai.handler@gmail.com \
    --cc=linux-rt-users@vger.kernel.org \
    /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).