From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: Tiezhu Yang <yangtiezhu@loongson.cn>, linux-mips@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Xuefeng Li <lixuefeng@loongson.cn>,
Juxin Gao <gaojuxin@loongson.cn>, Archer Yan <ayan@wavecomp.com>,
David Daney <david.daney@cavium.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: [QUESTION] support perf record --call-graph dwarf for mips
Date: Wed, 16 Dec 2020 19:14:02 +0800 [thread overview]
Message-ID: <90c7db1a-8e1a-e253-79ca-f93dbac014c2@flygoat.com> (raw)
In-Reply-To: <97fb66bf-51f8-a491-9eb4-10b2314cf82f@loongson.cn>
在 2020/12/16 下午6:05, Tiezhu Yang 写道:
> Hi,
>
> In the current upstream mainline kernel, perf record --call-graph dwarf
> is not supported for architecture mips64. I find the following related
> patches about this feature by David Daney <david.daney@cavium.com> and
> Archer Yan <ayan@wavecomp.com> in Sep 2019.
AFAIK ddaney left Cavium at 2018 and Wave Computing Shanghai is defuncted...
Feel free to take over if you like, there is no licenses issue, just
remember to credit
others properly.
- Jiaxun
>
> [1/2] Support mips unwinding and dwarf-regs
> https://lore.kernel.org/patchwork/patch/1126521/
>
> [2/2] Support extracting off-line stack traces from user-space with perf
> https://lore.kernel.org/patchwork/patch/1126520/
>
> Is this a work in progress?
> Could you please give me some feedback?
> Thank you for your help.
>
> Thanks,
> Tiezhu
next prev parent reply other threads:[~2020-12-16 11:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 10:05 [QUESTION] support perf record --call-graph dwarf for mips Tiezhu Yang
2020-12-16 11:14 ` Jiaxun Yang [this message]
2020-12-16 14:30 ` Arnaldo Carvalho de Melo
2020-12-16 15:16 ` Arnaldo Carvalho de Melo
2020-12-17 12:48 ` Tiezhu Yang
2020-12-21 8:12 ` Tiezhu Yang
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=90c7db1a-8e1a-e253-79ca-f93dbac014c2@flygoat.com \
--to=jiaxun.yang@flygoat.com \
--cc=acme@kernel.org \
--cc=ayan@wavecomp.com \
--cc=david.daney@cavium.com \
--cc=gaojuxin@loongson.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lixuefeng@loongson.cn \
--cc=yangtiezhu@loongson.cn \
/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.