mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Blunck <jblunck@suse.de>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] oprofile: Make callgraph use dump_trace() on i386/x86_64
Date: Fri, 10 Aug 2007 16:11:38 +0200	[thread overview]
Message-ID: <20070810141137.GG29553@hasse.suse.de> (raw)
In-Reply-To: <200708101545.22498.ak@suse.de>

On Fri, Aug 10, Andi Kleen wrote:

> On Friday 10 August 2007 15:35:29 jblunck@suse.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.

Yes, but before we didn't had any callgraphs for x86_64 since with
framepointers enabled the backtrace is having very strange results too.

I guess this is the best what we can achieve at the moment. Eventually when we
have fast, precise backtraces in the kernel the oprofile code benefits from
that automatically with this patch.

  reply	other threads:[~2007-08-10 14:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-10 13:35 [PATCH 0/2] Improve Oprofile Callgraphs " jblunck
2007-08-10 13:35 ` [PATCH 1/2] oprofile: Make callgraph use dump_trace() " jblunck
2007-08-10 13:45   ` Andi Kleen
2007-08-10 14:11     ` Jan Blunck [this message]
2007-08-10 13:35 ` [PATCH 2/2] i386/x86_64: Introduce frame_pointer() and stack_pointer() jblunck

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=20070810141137.GG29553@hasse.suse.de \
    --to=jblunck@suse.de \
    --cc=ak@suse.de \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®