All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Ivan Jiang <jcgeforce@aliyun.com>, xenomai@xenomai.org
Subject: Re: Can I use ftrace to analysis cobalt kernel
Date: Tue, 24 Aug 2021 15:21:57 +0200	[thread overview]
Message-ID: <88960bcc-c77b-78a4-dd9c-5d5f7c81e4ce@siemens.com> (raw)
In-Reply-To: <2EEA4F9C-7739-425E-B57E-1BED69207E6B@aliyun.com>

On 24.08.21 14:48, Ivan Jiang via Xenomai wrote:
> Dear guys:
> 
>  
> 
>        Can I use ftrace to analysis the kernel with patch of ipipe.
> 
>        I find if use function_graph whe kernel will crash like below:
> 
>        echo function_graph > current_tracer
> 
> root@smarc-rzg2l:/sys/kernel/debug/tracing# [  377.392724] Kernel panic - not syncing: kernel stack overflow
> 
> [  377.399125] CPU: 0 PID: 9 Comm: ksoftirqd/0 Not tainted 4.19.140-cip33-g6634f0243a91 #3
> 
> [  377.407929] Hardware name: RZG2L Evaluation Board Kit (Discrete Power System Ver.) (Dual Cortex-A55) (DT)
> 

That's ARM64 and I-pipe - might not have been tested / fully enabled in
that combination. Try 5.10 with the dovetail patch, there ftrace is
known to work better. Alternatively: the I-pipe tracer should work on
arm64 (though without a nice function graph).

Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux


  reply	other threads:[~2021-08-24 13:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-24 12:48 Can I use ftrace to analysis cobalt kernel Ivan Jiang
2021-08-24 13:21 ` Jan Kiszka [this message]
2021-08-24 14:50   ` Greg Gallagher
2021-08-25  2:30     ` Ivan Jiang

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=88960bcc-c77b-78a4-dd9c-5d5f7c81e4ce@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=jcgeforce@aliyun.com \
    --cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.