All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Ahern" <daahern@cisco.com>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf tools: Add rootfs option for off-box analysis using specified tree
Date: Sun, 21 Nov 2010 10:02:24 -0700	[thread overview]
Message-ID: <4CE950A0.2060705@cisco.com> (raw)
In-Reply-To: <20101121163455.GA4024@ghostprotocols.net>



On 11/21/10 09:34, Arnaldo Carvalho de Melo wrote:
> Em Sun, Nov 21, 2010 at 09:17:55AM -0700, y@cisco.com escreveu:
>> From: David Ahern <daahern@cisco.com>
>>
>> The rootfs argument allows analysis of perf.data file using a locally
>> accessible filesystem tree with debug symbols - e.g.,  loop mounted
>> KVM disk images, NFS, 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.
> 
> Patch looks sane after quick look, just in doubt if "rootfs" is a good
> name for this, will look if this can be somehow combined with the kvm
> parameters.

I do want to have the ability to analyze a KVM hosted VM using an
external tree as well. e.g., --guestmount points to an sshfs mount and
--rootfs points to a tree with symbols for the stripped image running in
the VM.

I think my followup patch for kallsyms should be able to leverage some
of the guestkallsyms code from KVM.

David

> 
> Anybody else with cycles to think about this?
> 
> - Arnaldo

  reply	other threads:[~2010-11-21 17:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1290356275-9969-1-git-send-email-y>
2010-11-21 16:34 ` [PATCH] perf tools: Add rootfs option for off-box analysis using specified tree Arnaldo Carvalho de Melo
2010-11-21 17:02   ` David S. Ahern [this message]
2010-11-21 18:12     ` Arnaldo Carvalho de Melo
2010-11-21 16:19 David Ahern
  -- strict thread matches above, loose matches on Subject: below --
2010-11-21 16:17 y

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=4CE950A0.2060705@cisco.com \
    --to=daahern@cisco.com \
    --cc=acme@ghostprotocols.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.