public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pradeep Kumar Surisetty <psuriset@linux.vnet.ibm.com>
To: David Ahern <dsahern@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, ryanh@linux.vnet.ibm.com
Subject: Re: perf kvm segfaults while reporting events
Date: Wed, 20 Jun 2012 11:44:23 +0530	[thread overview]
Message-ID: <20120620061423.GB3488@linux.vnet.ibm.com> (raw)
In-Reply-To: <4FC8E26E.7060309@gmail.com>

* David Ahern <dsahern@gmail.com> [2012-06-01 09:40:30]:

> On 6/1/12 7:56 AM, Pradeep Kumar Surisetty wrote:
> >Hello
> >
> >perf kvm generats segfaults while reporting events.
> >
> >host&  guest:  3.4.0-rc4
> >
> >1) Copied kallsyms, modules from guest to host.
> >
> >2) recorded  events on host and guest&  report it using below commands.
> >
> >
> >[root@host]# ./perf kvm --host --guest --guestkallsyms=/tmp/guest-kallsyms --guestmodules=/tmp/guest-modules record -a -o perf.data
> >^C[ perf record: Woken up 1 times to write data ]
> >[ perf record: Captured and wrote 0.381 MB perf.data (~16659 samples) ]
> >
> >[root@host]# ./perf kvm --host --guest --guestkallsyms=/tmp/guest-kallsyms --guestmodules=/tmp/guest-modules report -i perf.data --force
> >perf: Segmentation fault
> 
> The short of it is that perf-kvm needs some work.
> 
> More specifically, the guest 'machine' is not created on the report
> path for the above arguments. This will prevent the segfault:
> 
> diff --git a/tools/perf/util/session.c b/tools/perf/util/session.c
> index 93d355d..c8e1323 100644
> --- a/tools/perf/util/session.c
> +++ b/tools/perf/util/session.c
> @@ -918,6 +918,8 @@ static int perf_session_deliver_event(struct
> perf_session *session,
>         }
>         return tool->sample(tool, event, sample, evsel, machine);
>     case PERF_RECORD_MMAP:
> +       if (machine == NULL)
> +           return 0;


Ahhh perf kvm works fine if we record guest events for enough time. 
above patch works better, if some one doesnt record for adequate time. 


>         return tool->mmap(tool, event, sample, machine);
>     case PERF_RECORD_COMM:
>         return tool->comm(tool, event, sample, machine);
> 
> 
> The --guestmount option (which has its own problems) combined with
> specific pid is more stable . e.g.,
> 
> mkdir /tmp/guestmount/<vm-pid>
> sshfs root@<vm-ip>:/  /tmp/guestmount/<vm-pid> -o direct_io
> 
> perf kvm --host --guest --guestmount=/tmp/guestmount \
>   record -p <vm-pid>  -o /tmp/perf.data -- sleep 1
> 
> perf kvm --host --guest --guestmount=/tmp/guestmount  report -i
> /tmp/perf.data --force --stdio
> 
> If you use the -a argument on record with multiple VMs running
> without an entry in /tmp/guestmount you'll see:
> 
> Warning:
> 7 unprocessable samples recorded.
> Do you have a KVM guest running and not using 'perf kvm'?
> 
> David
> 


  reply	other threads:[~2012-06-20  6:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-01 13:56 perf kvm segfaults while reporting events Pradeep Kumar Surisetty
2012-06-01 15:40 ` David Ahern
2012-06-20  6:14   ` Pradeep Kumar Surisetty [this message]
2012-06-25  3:38     ` David Ahern

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=20120620061423.GB3488@linux.vnet.ibm.com \
    --to=psuriset@linux.vnet.ibm.com \
    --cc=dsahern@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ryanh@linux.vnet.ibm.com \
    /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