From: David Ahern <dsahern@gmail.com>
To: Adrian Hunter <adrian.hunter@intel.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: more perf breakage from sample identifier
Date: Thu, 05 Sep 2013 15:56:12 -0600 [thread overview]
Message-ID: <5228FDFC.9090700@gmail.com> (raw)
In-Reply-To: <5228F92A.9020108@gmail.com>
On 9/5/13 3:35 PM, David Ahern wrote:
> Adrian:
>
> 'perf kvm stat live' command fails on Linus' latest tree:
> $ perf kvm stat live
> Failed to parse sample
>
> git bisect points to:
>
> 75562573bab35b129cfd342fc2bcf89da84a6644 is the first bad commit
> commit 75562573bab35b129cfd342fc2bcf89da84a6644
> Author: Adrian Hunter <adrian.hunter@intel.com>
> Date: Tue Aug 27 11:23:09 2013 +0300
>
> perf tools: Add support for PERF_SAMPLE_IDENTIFIER
>
> Enable parsing of samples with sample format bit
> PERF_SAMPLE_IDENTIFIER.
> In addition, if the kernel supports it, prefer it to selecting
> PERF_SAMPLE_ID thereby allowing non-matching sample types.
>
> Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
>
>
> perf_evlist__event2evsel() is failing. From what I can see the problem
> is that evlist->heads is not getting populated. This command does not
> read/write files but processes events as they come in. I have another
> similar command that is also breaking for the same reason.
That's not the problem. The hash is getting populated. The problem is a
bad assumption on what fields are in the sample -- like PERF_SAMPLE_IP.
The kvm command does not care about the IP so it is excluded:
attr->sample_type &= ~PERF_SAMPLE_IP;
If I remove that line the command works fine.
Since this a legitimate option to not get the IP in the sample, the
evsel lookup code needs to get fixed in 3.12.
David
prev parent reply other threads:[~2013-09-05 21:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 21:35 more perf breakage from sample identifier David Ahern
2013-09-05 21:56 ` David Ahern [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=5228FDFC.9090700@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=adrian.hunter@intel.com \
--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