From: Noel Grandin <noelgrandin@gmail.com>
To: Jiri Olsa <jolsa@kernel.org>, Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>, Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH 0/6] perf tools: Various fixes
Date: Fri, 18 Dec 2015 11:06:56 +0200 [thread overview]
Message-ID: <5673CCB0.4000607@gmail.com> (raw)
In-Reply-To: <1450384015-12367-1-git-send-email-jolsa@kernel.org>
This series is
Tested-By: Noel Grandin <noelgrandin@gmail.com>
On 2015-12-17 10:26 PM, Jiri Olsa wrote:
> hi,
> sending several changes together:
> - leftover for the stat enable/disable changes with Adrian's patch
> - fixes for issues Noel found with DWARF unwind
>
> Noel, could you please rerun your test on this?
>
> Also available in:
> git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
> perf/fixes
>
> thanks,
> jirka
>
>
> ---
> Adrian Hunter (1):
> perf tools: Make perf_evlist__open() open evsels with their cpus and threads (like perf record does)
>
> Jiri Olsa (5):
> perf tools: Remove perf_evlist__(enable|disable)_event functions
> perf tools: Use find_map function in access_dso_mem
> perf tools libunwind: Check for mmaps also in MAP__VARIABLE tree
> perf tools libdw: Check for mmaps also in MAP__VARIABLE tree
> perf record: Always store data mmaps
>
> tools/perf/arch/x86/util/intel-bts.c | 4 ++--
> tools/perf/arch/x86/util/intel-pt.c | 4 ++--
> tools/perf/builtin-kvm.c | 2 +-
> tools/perf/builtin-record.c | 2 +-
> tools/perf/builtin-top.c | 2 +-
> tools/perf/builtin-trace.c | 2 +-
> tools/perf/tests/code-reading.c | 2 +-
> tools/perf/tests/dwarf-unwind.c | 2 +-
> tools/perf/tests/keep-tracking.c | 2 +-
> tools/perf/tests/mmap-thread-lookup.c | 4 ++--
> tools/perf/tests/switch-tracking.c | 6 +++---
> tools/perf/util/event.c | 16 ++++++----------
> tools/perf/util/event.h | 5 ++---
> tools/perf/util/evlist.c | 44 +-------------------------------------------
> tools/perf/util/evlist.h | 4 ----
> tools/perf/util/machine.c | 6 +++---
> tools/perf/util/machine.h | 6 +++---
> tools/perf/util/unwind-libdw.c | 10 ++++++++++
> tools/perf/util/unwind-libunwind.c | 20 ++++++++++++++------
> 19 files changed, 55 insertions(+), 88 deletions(-)
>
next prev parent reply other threads:[~2015-12-18 9:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 20:26 [PATCH 0/6] perf tools: Various fixes Jiri Olsa
2015-12-17 20:26 ` [PATCH 1/6] perf tools: Remove perf_evlist__(enable|disable)_event functions Jiri Olsa
2015-12-17 20:26 ` [PATCH 2/6] perf tools: Make perf_evlist__open() open evsels with their cpus and threads (like perf record does) Jiri Olsa
2015-12-17 20:26 ` [PATCH 3/6] perf tools: Use find_map function in access_dso_mem Jiri Olsa
2015-12-17 20:26 ` [PATCH 4/6] perf tools libunwind: Check for mmaps also in MAP__VARIABLE tree Jiri Olsa
2015-12-17 20:26 ` [PATCH 5/6] perf tools libdw: " Jiri Olsa
2015-12-17 20:26 ` [PATCH 6/6] perf record: Always store data mmaps Jiri Olsa
2016-01-05 11:16 ` Namhyung Kim
2016-01-05 14:11 ` Jiri Olsa
2015-12-17 20:49 ` [PATCH 0/6] perf tools: Various fixes Jiri Olsa
2015-12-18 9:06 ` Noel Grandin [this message]
2015-12-27 11:57 ` Jiri Olsa
2016-01-05 10:23 ` Jiri Olsa
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=5673CCB0.4000607@gmail.com \
--to=noelgrandin@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@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