linux-kernel - [Q] Perf-events callchain support on MIPS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTikb5jAw_fSQ08IMrzwKK7lfafXlm63S46F-C8m0@mail.gmail.com>
Date:	Sun, 6 Jun 2010 07:41:34 +0800
From:	Deng-Cheng Zhu <dengcheng.zhu@...il.com>
To:	mingo@...e.hu, peterz@...radead.org
Cc:	linux-kernel@...r.kernel.org
Subject: [Q] Perf-events callchain support on MIPS

Hi, Peter and Ingo

For MIPS, recording user stack backtrace in the kernel is not quite as easy
as on other platforms. Because In the kernel, we don't have frame unwinder
to work on the user stack. Given the different possible compiler flags,
getting the backtrace for the user stack is especially challenging.

So, is it still useful to implement the Perf-events callchain support on
MIPS with only kernel addresses recorded for now? What impact do you see to
do so? Only that the user can not see user-level performance bottleneck?

Thanks!

Deng-Cheng
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/