public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Arnaldo Carvalho de Melo" <acme@redhat.com>,
	"Paul Mackerras" <paulus@samba.org>,
	"Frédéric Weisbecker" <fweisbec@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"Peter Zijlstra" <a.p.zijlstra@chello.nl>
Subject: Re: [patch 0/4] perf_counter tools: support annotation of live kernel modules
Date: Thu, 02 Jul 2009 09:17:56 +0200	[thread overview]
Message-ID: <1246519076.6384.22.camel@marge.simson.net> (raw)
In-Reply-To: <20090702064712.GA26690@elte.hu>

On Thu, 2009-07-02 at 08:47 +0200, Ingo Molnar wrote:
> * Mike Galbraith <efault@gmx.de> wrote:
> 
> > Per $subject, this patch set only supports for the LIVE kernel.  
> > It adds support infrastructure for path discovery, load address 
> > lookup, and symbol generation of live kernel modules.
> > 
> > TODO includes resurrection of live annotation in perf top, and 
> > support for annotation and report generation of other than live 
> > modules.  As the patch set sits, Perf top can generate symbols 
> > from live binaries, but there's no live annotation capability yet.
> > 
> > patch1: perf_counter tools: Make symbol loading consistently return number of loaded symbols.
> > patch2: perf_counter tools: Add infrastructure to support loading of kernel module symbols
> > patch3: perf_counter tools: connect module support infrastructure to symbol loading infrastructure
> > patch4: perf_counter tools: Enable kernel module symbol loading in tools
> > 
> > Comments and suggestions most welcome.
> 
> Looks very nice! I've applied it with a few minor stylistic fixlets 
> and a tad more verbose changelogs.

Thanks!

(sorry about changelogs, I did stare at them, nothing spiffy happened)

> I'm wondering about the next step: couldnt we somehow guess at the 
> position of the vmlinux too, validate somehow that it corresponds to 
> the kernel we are running - and then use it automatically and by 
> default?

I don't know of a way to discover where the image lives.  Been pondering
that very thing, along with idiot-proofing.

> Plus, offline analysis would be nice as well i suspect - being able 
> to look at profiles on a different box?

Yes, that's high on my TODO.  I've been pondering a perf archive tool
that would package everything that's needed to do analysis on a
different box.  One big problem though, is that while you can easily
package vmlinux and modules, what about all the userland binaries?  A
large perf.data and/or debug info binaries can easily make transport
impractical enough.

After I resurrect (well, try) live annotation in top, I'll fiddle with
offline kernel analysis.

	-Mike


  reply	other threads:[~2009-07-02  7:18 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02  6:03 [patch 0/4] perf_counter tools: support annotation of live kernel modules Mike Galbraith
2009-07-02  6:05 ` [patch 1/4] perf_counter tools: Make symbol loading consistently return number of loaded symbols Mike Galbraith
2009-07-02  7:06   ` [tip:perfcounters/urgent] " tip-bot for Mike Galbraith
2009-07-02  6:07 ` [patch 2/4] perf_counter tools: Add infrastructure to support loading of kernel module symbols Mike Galbraith
2009-07-02  7:06   ` [tip:perfcounters/urgent] " tip-bot for Mike Galbraith
2009-07-02  6:08 ` [patch 3/4] perf_counter tools: connect module support infrastructure to symbol loading infrastructure Mike Galbraith
2009-07-02  7:06   ` [tip:perfcounters/urgent] perf_counter tools: Connect " tip-bot for Mike Galbraith
2009-07-02  6:09 ` [patch 4/4] perf_counter tools: Enable kernel module symbol loading in tools Mike Galbraith
2009-07-02  7:07   ` [tip:perfcounters/urgent] " tip-bot for Mike Galbraith
2009-07-02  6:47 ` [patch 0/4] perf_counter tools: support annotation of live kernel modules Ingo Molnar
2009-07-02  7:17   ` Mike Galbraith [this message]
2009-07-02  7:42     ` Ingo Molnar
2009-07-02  7:55       ` Mike Galbraith
2009-07-03  7:27         ` Ingo Molnar
2009-07-03  7:36           ` Mike Galbraith
2009-07-02  8:42     ` Mike Galbraith
2009-07-02  8:53       ` Mike Galbraith
2009-07-03  7:29       ` Ingo Molnar
2009-07-03  8:00         ` Mike Galbraith
2009-07-03  8:15           ` Ingo Molnar
2009-07-03  8:28             ` Mike Galbraith
2009-07-03  8:53               ` Frederic Weisbecker
2009-07-02 12:10     ` Peter Zijlstra
2009-07-03  7:17       ` Mike Galbraith
2009-07-03  7:24         ` Ingo Molnar
2009-07-03  7:31           ` Jaswinder Singh Rajput
2009-07-03  8:41         ` Frederic Weisbecker
2009-07-03  8:53           ` Ingo Molnar

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=1246519076.6384.22.camel@marge.simson.net \
    --to=efault@gmx.de \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.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