linux-kernel - Re: [PATCH] x86: add the debugfs interface for the sysprof tool

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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 26 Feb 2008 08:27:32 +0200
From:	"Pekka Enberg" <penberg@...helsinki.fi>
To:	"Nicholas Miell" <nmiell@...cast.net>
Cc:	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Arjan van de Ven" <arjan@...radead.org>,
	linux-kernel@...r.kernel.org, mingo@...e.hu, sandmann@...hat.com,
	tglx@...x.de, hpa@...or.com, levon@...ementarian.org
Subject: Re: [PATCH] x86: add the debugfs interface for the sysprof tool

On Sun, Feb 24, 2008 at 5:12 AM, Nicholas Miell <nmiell@...cast.net> wrote:
> > Sysprof tracks the full stack frame so it can provide meaningful call
> > tree (who called what) which is invaluable for spotting hot _paths_. I
> > don't see how oprofile can do that as it tracks instruction pointers only.
>
>  You could try passing the --callgraph option to opcontrol.

Hmm, perhaps I am missing something but I don't think that does what
sysprof does. At least I can't find where in the oprofile kernel code
does it save the full stack trace for user-space. John?

                        Pekka
--
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/