linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: David Ahern <daahern@cisco.com>
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH-v2] perf tools: Add symfs option for off-box analysis using specified tree
Date: Thu, 9 Dec 2010 15:14:36 -0200	[thread overview]
Message-ID: <20101209171436.GA13027@ghostprotocols.net> (raw)
In-Reply-To: <1291862020-24540-1-git-send-email-daahern@cisco.com>

Em Wed, Dec 08, 2010 at 07:33:40PM -0700, David Ahern escreveu:
> The symfs argument allows analysis of perf.data file using a locally
> accessible filesystem tree with debug symbols - e.g., tree created
> during image builds, sshfs mount, loop mounted KVM disk images,
> USB keys, initrds, etc. Anything with an OS tree can be analyzed from
> anywhere without the need to populate a local data store with
> build-ids.
> 
> Signed-off-by: David Ahern <daahern@cisco.com>
> 
> v1 --> v2: removed symfs changes from builtin-annotate.c
>            fixed tab/space inconsistencies
>            changed new strlen() to symbol_conf.symfs[0]
>            added symfs option to Documentation files

So I tried it now with:

perf report --symfs /

Which should be equivalent to the common case:

perf report

Bu kernel symbols didn't got resolved, can you please check this?

- Arnaldo

      reply	other threads:[~2010-12-09 17:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09  2:33 [PATCH-v2] perf tools: Add symfs option for off-box analysis using specified tree David Ahern
2010-12-09 17:14 ` Arnaldo Carvalho de Melo [this message]

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=20101209171436.GA13027@ghostprotocols.net \
    --to=acme@ghostprotocols.net \
    --cc=daahern@cisco.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@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;
as well as URLs for NNTP newsgroup(s).