From: Ingo Molnar <mingo@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
Alexei Starovoitov <ast@kernel.org>,
Don Zickus <dzickus@redhat.com>,
Douglas Hatch <doug.hatch@hp.com>, Jiri Olsa <jolsa@redhat.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
pi3orama@163.com, Scott J Norton <scott.norton@hp.com>,
Waiman Long <Waiman.Long@hp.com>, Wang Nan <wangnan0@huawei.com>,
Zefan Li <lizefan@huawei.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [GIT PULL 0/5] perf/urgent fixes
Date: Wed, 18 Nov 2015 06:57:53 +0100 [thread overview]
Message-ID: <20151118055753.GA29994@gmail.com> (raw)
In-Reply-To: <1447448249-22276-1-git-send-email-acme@kernel.org>
* Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> The following changes since commit 2059fc7a5a9e667797b8ec503bfb4685afee48d8:
>
> perf symbols: Allow forcing reading of non-root owned files by root (2015-11-12 18:58:18 -0300)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-urgent-for-mingo
>
> for you to fetch changes up to 092b1f0b5f9f797812da0de927c3aa26acbe8762:
>
> perf probe: Clear probe_trace_event when add_probe_trace_event() fails (2015-11-13 12:28:09 -0300)
>
> ----------------------------------------------------------------
> perf/urgent fixes:
>
> - Do not change the key of an object in a rbtree, this time it was
> the one for DSOs lookup by its long_name, and the noticed symptom was
> with 'perf buildid-list --with-hits' (Adrian Hunter)
>
> - 'perf inject' is a pipe, events it doesn't touch should be passed
> on, PERF_RECORD_LOST wasn't, fix it (Adrian Hunter)
>
> - Make 'perf buildid-list' request event ordering, as it needs to
> first get the mmap events to be able to mark wich DSOs had hits
> (Adrian Hunter)
>
> - Fix memory leaks on failure in 'perf probe' (Masami Hiramatsu, Wang Nan)
>
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
>
> ----------------------------------------------------------------
> Adrian Hunter (3):
> perf symbols: Fix dso lookup by long name and missing buildids
> perf buildid-list: Requires ordered events
> perf inject: Also re-pipe lost_samples event
>
> Masami Hiramatsu (1):
> perf probe: Fix memory leaking on failure by clearing all probe_trace_events
>
> Wang Nan (1):
> perf probe: Clear probe_trace_event when add_probe_trace_event() fails
>
> tools/perf/builtin-inject.c | 1 +
> tools/perf/util/build-id.c | 1 +
> tools/perf/util/dso.c | 17 +++++++++++++++++
> tools/perf/util/dso.h | 1 +
> tools/perf/util/machine.c | 1 +
> tools/perf/util/probe-finder.c | 24 +++++++++++++++++-------
> 6 files changed, 38 insertions(+), 7 deletions(-)
Pulled, thanks a lot Arnaldo!
Ingo
next prev parent reply other threads:[~2015-11-18 5:57 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 20:57 Arnaldo Carvalho de Melo
2015-11-13 20:57 ` [PATCH 1/5] perf symbols: Fix dso lookup by long name and missing buildids Arnaldo Carvalho de Melo
2015-11-13 20:57 ` [PATCH 2/5] perf buildid-list: Requires ordered events Arnaldo Carvalho de Melo
2015-11-13 20:57 ` [PATCH 3/5] perf inject: Also re-pipe lost_samples event Arnaldo Carvalho de Melo
2015-11-13 20:57 ` [PATCH 4/5] perf probe: Fix memory leaking on failure by clearing all probe_trace_events Arnaldo Carvalho de Melo
2015-11-13 20:57 ` [PATCH 5/5] perf probe: Clear probe_trace_event when add_probe_trace_event() fails Arnaldo Carvalho de Melo
2015-11-18 5:57 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-05 16:10 [GIT PULL 0/5] perf/urgent fixes Arnaldo Carvalho de Melo
2018-10-05 16:14 ` Ingo Molnar
2018-07-30 20:50 Arnaldo Carvalho de Melo
2018-07-31 5:51 ` Ingo Molnar
2018-05-14 12:23 Arnaldo Carvalho de Melo
2018-05-15 6:21 ` Ingo Molnar
2017-12-18 14:39 Arnaldo Carvalho de Melo
2017-12-18 17:11 ` Ingo Molnar
2015-12-07 20:06 Arnaldo Carvalho de Melo
2015-12-08 5:09 ` Ingo Molnar
2015-11-11 21:56 Arnaldo Carvalho de Melo
2015-11-12 6:38 ` Ingo Molnar
2015-09-17 18:54 Arnaldo Carvalho de Melo
2015-09-18 5:46 ` Ingo Molnar
2014-02-13 21:15 Arnaldo Carvalho de Melo
2014-02-22 16:23 ` Ingo Molnar
2013-11-19 20:41 Arnaldo Carvalho de Melo
2013-11-20 13:32 ` Ingo Molnar
2013-09-10 18:11 Arnaldo Carvalho de Melo
2013-09-11 5:46 ` Ingo Molnar
2013-09-11 5:55 ` Ingo Molnar
2013-09-11 14:08 ` Arnaldo Carvalho de Melo
2013-09-12 5:45 ` Ingo Molnar
2013-12-02 6:58 ` Brian Gitonga Marete
2012-04-14 17:03 Arnaldo Carvalho de Melo
2012-04-15 6:04 ` Ingo Molnar
2012-04-05 23:28 Arnaldo Carvalho de Melo
2011-05-27 21:45 Arnaldo Carvalho de Melo
2011-05-28 9:41 ` Ingo Molnar
2011-05-29 14:12 ` Arnaldo Carvalho de Melo
2011-05-29 14:30 ` Ingo Molnar
2011-04-06 11:00 Arnaldo Carvalho de Melo
2011-04-06 11:10 ` Ingo Molnar
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=20151118055753.GA29994@gmail.com \
--to=mingo@kernel.org \
--cc=Waiman.Long@hp.com \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=ast@kernel.org \
--cc=doug.hatch@hp.com \
--cc=dzickus@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=pi3orama@163.com \
--cc=scott.norton@hp.com \
--cc=wangnan0@huawei.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
Powered by JetHome