linux-kernel - Re: [PATCH 1/2] oprofile: Make callgraph use dump_trace() on i386/x86

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]

Message-Id: <200708101545.22498.ak@suse.de>
Date:	Fri, 10 Aug 2007 15:45:22 +0200
From:	Andi Kleen <ak@...e.de>
To:	jblunck@...e.de
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] oprofile: Make callgraph use dump_trace() on i386/x86_64

On Friday 10 August 2007 15:35:29 jblunck@...e.de wrote:
> This patch improves oprofile callgraphs for i386/x86_64. The old backtracing
> code was unable to produce even kernel backtraces if the kernel wasn't
> compiled with framepointers. The code now uses dump_trace().

Hmm one issue i didn't notice before: with imprecise backtrace
the profiling could be a little random because even if the same
call chain is hit repeatedly the garbage left over stack entries also
reported could vary and then cause oprofile to put it into different
buckets. But there is probably not much that can be 
done about that.

-Andi

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