* Arnaldo Carvalho de Melo <a...@kernel.org> wrote:
> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> The following changes since commit d7a702f0b1033cf402fef65bd6395072738f0844:
>
> perf/x86/intel/cqm: Do not access cpu_data() from CPU_UP_PREPARE handler
> (2015-08-12 11:37:23 +0200)
>
> 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 09f4d78ab0af0973e1a49c10eb7bf977c68cc3aa:
>
> perf top: Show backtrace when handling a SIGSEGV on --stdio mode
> (2015-08-19 15:16:08 -0300)
>
> ----------------------------------------------------------------
> perf/urgent fixes:
>
> User visible:
>
> - Fix buildid processing done at the end of a 'perf record' session, a
> problem that happened in workloads involving lots of small short-lived
> processes. That code was not asking the perf_session layer to order
> the events.
>
> Make the code more robust to handle some of the problems with such
> out-of-order events and fix 'perf record' to ask for ordered events
> on systems where we have perf_event_attr.sample_id_all. (Adrian Hunter)
>
> - Show backtrace when handling a SIGSEGV in 'perf top --stdio' (Arnaldo
> Carvalho de Melo)
>
> Signed-off-by: Arnaldo Carvalho de Melo <a...@redhat.com>
>
> ----------------------------------------------------------------
> Adrian Hunter (3):
> perf tools: Avoid deadlock when map_groups are broken
> perf tools: Make fork event processing more resilient
> perf tools: Fix buildid processing
>
> Arnaldo Carvalho de Melo (1):
> perf top: Show backtrace when handling a SIGSEGV on --stdio mode
>
> tools/perf/builtin-record.c | 11 +++++++++++
> tools/perf/builtin-top.c | 4 ++--
> tools/perf/util/machine.c | 20 ++++++++++++++++++--
> tools/perf/util/thread.c | 6 ++++++
> 4 files changed, 37 insertions(+), 4 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 majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
