Re: [GIT PULL 0/3] perf/urgent fixes

[Ingo Molnar]

* Arnaldo Carvalho de Melo <acme@xxxxxxxxxx> wrote:

> Hi Ingo,
> 
> 	Please consider pulling,
> 
> - Arnaldo
> 
> The following changes since commit ed9eb845d7916b2bc863e5b93c82e18be8faf032:
> 
>   Merge tag 'perf-urgent-for-mingo' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/urgent (2015-01-08 08:59:22 +0100)
> 
> 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 c09e31cc128cf1aec3a6cd47203508fbf0082873:
> 
>   perf hists browser: Fix segfault when showing callchain (2015-01-08 11:59:16 -0300)
> 
> ----------------------------------------------------------------
> perf/urgent fixes:
> 
> . Free callchains when hist entries are deleted, plugging a massive leak in
>   'top -g', where hist_entries (and its callchains) are decayed over time. (Namhyung Kim)
> 
> . Fix segfault when showing callchain in the hists browser (report & top) (Namhyung Kim)
> 
> . Fix children sort key behavior, and also the 'perf test 32' test that
>   was failing due to reliance on undefined behaviour (Namhyung Kim)
> 
> Signed-off-by: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
> 
> ----------------------------------------------------------------
> Namhyung Kim (3):
>       perf hists: Fix children sort key behavior
>       perf callchain: Free callchains when hist entries are deleted
>       perf hists browser: Fix segfault when showing callchain
> 
>  tools/perf/tests/hists_cumulate.c | 64 +++++++++++++++++++--------------------
>  tools/perf/ui/browsers/hists.c    |  2 +-
>  tools/perf/ui/hist.c              |  3 ++
>  tools/perf/util/callchain.c       | 30 ++++++++++++++++++
>  tools/perf/util/callchain.h       |  2 ++
>  tools/perf/util/hist.c            |  1 +
>  6 files changed, 69 insertions(+), 33 deletions(-)

Pulled, thanks a lot Arnaldo!

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/