From: David Ahern <dsahern@gmail.com>
To: Adrian Hunter <adrian.hunter@intel.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux-kernel@vger.kernel.org,
Frederic Weisbecker <fweisbec@gmail.com>,
Jiri Olsa <jolsa@redhat.com>, Mike Galbraith <efault@gmx.de>,
Namhyung Kim <namhyung@gmail.com>,
Paul Mackerras <paulus@samba.org>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH 2/2] perf tools: fix parsing with no sample_id_all bit set
Date: Wed, 04 Sep 2013 15:45:55 -0600 [thread overview]
Message-ID: <5227AA13.7090300@gmail.com> (raw)
In-Reply-To: <1378325897-3840-3-git-send-email-adrian.hunter@intel.com>
On 9/4/13 2:18 PM, Adrian Hunter wrote:
> The perf_evlist__event2evsel() is changed to handle
> non-sample events (such as mmap events) that have no
> id sample appended i.e. when sample_id_all is not set.
>
> Note that such events have a fixed format, so that
> the selected event (evsel) they are associated with
> is immaterial.
>
> Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
Fixes the regression. Thanks for the fix.
Tested-and-Acked-by: David Ahern <dsahern@gmail.com>
Arnaldo: this needs to go in perf/urgent and pushed into 3.12.
David
next prev parent reply other threads:[~2013-09-04 21:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 20:18 [PATCH 0/2] perf tools: fix parsing with no sample_id_all bit set Adrian Hunter
2013-09-04 20:18 ` [PATCH 1/2] perf tools: add test for parsing with no sample_id_all bit Adrian Hunter
2013-09-06 12:13 ` [tip:perf/urgent] perf tools: Add " tip-bot for Adrian Hunter
2013-09-04 20:18 ` [PATCH 2/2] perf tools: fix parsing with no sample_id_all bit set Adrian Hunter
2013-09-04 21:45 ` David Ahern [this message]
2013-09-06 12:14 ` [tip:perf/urgent] perf evlist: Fix " tip-bot for Adrian Hunter
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=5227AA13.7090300@gmail.com \
--to=dsahern@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=adrian.hunter@intel.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@gmail.com \
--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 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.