From: Arnd Bergmann <arnd@arndb.de>
To: davidm@hpl.hp.com
Cc: linux-arch@vger.kernel.org, davidm@napali.hpl.hp.com,
Wolfgang Gellerich <gellerich@de.ibm.com>
Subject: Re: other platforms interested in in-kernel unwinder?
Date: Fri, 3 Dec 2004 10:37:22 +0100 [thread overview]
Message-ID: <200412031037.22445.arnd@arndb.de> (raw)
In-Reply-To: <16815.21943.55627.572012@napali.hpl.hp.com>
[-- Attachment #1: Type: text/plain, Size: 787 bytes --]
On Dunnersdag 02 Dezember 2004 18:49, David Mosberger wrote:
> So, how does this sound? Any interest from say, x86{-64}, PPC, SPARC,
> or any other arch maintainer?
I think it doesn't make much sense for unwinding s390 kernel stacks,
since they already have reliable back traces trough the backchain
pointers. In particular, those pointers are needed anyway for easy
unwinding by hand when debugging in z/VM.
My limited experience on ppc64 suggests that the situation there
is very similar.
OTOH, I've heard that oprofile is unwinding user stacks to get call
graph information. For that purpose, a kernel unwinder might turn
out very valuable on many architectures, including those that use
a backchain pointer in kernel but not in user space.
Arnd <><
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-12-03 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 17:49 other platforms interested in in-kernel unwinder? David Mosberger
2004-12-03 9:37 ` Arnd Bergmann [this message]
2004-12-03 21:09 ` David Mosberger
2004-12-03 22:56 ` Arnd Bergmann
2004-12-03 23:22 ` David Mosberger
2004-12-04 3:59 ` Paul Mackerras
2004-12-04 21:04 ` David Mosberger
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=200412031037.22445.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=davidm@hpl.hp.com \
--cc=davidm@napali.hpl.hp.com \
--cc=gellerich@de.ibm.com \
--cc=linux-arch@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