linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Clark Williams <williams@redhat.com>,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	Andi Kleen <ak@linux.intel.com>, He Kuang <hekuang@huawei.com>,
	Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
	Song Liu <liu.song.a23@gmail.com>,
	Stephane Eranian <eranian@google.com>, Tony Jones <tonyj@suse.de>,
	Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [GIT PULL 0/7] perf/urgent fixes
Date: Tue, 22 Jan 2019 12:30:08 +0100	[thread overview]
Message-ID: <20190122113008.GB113758@gmail.com> (raw)
In-Reply-To: <20190121183507.23490-1-acme@kernel.org>


* Arnaldo Carvalho de Melo <acme@kernel.org> wrote:

> Hi Ingo,
> 
> 	Please consider pulling,
> 
> Regards,
> 
> - Arnaldo
> 
> Test results at the end of this message, as usual.
> 
> The following changes since commit 4e72ee8872279a70ebe973172133b98e8acbf54e:
> 
>   Merge tag 'perf-core-for-mingo-5.0-20190110' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/urgent (2019-01-11 08:12:09 +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-5.0-20190121
> 
> for you to fetch changes up to 8bf8c6da53c2265aea365a1de6038f118f522113:
> 
>   perf script: Fix crash when processing recorded stat data (2019-01-21 11:29:07 -0300)
> 
> ----------------------------------------------------------------
> perf/urgent fixes:
> 
> Kernel:
> 
>   Stephane Eranian:
> 
>   - Fix perf_proc_update_handler() bug.
> 
> perf script:
> 
>   Andi Kleen:
> 
>   - Fix crash with printing mixed trace point and other events.
> 
>   Tony Jones:
> 
>   - Fix crash when processing recorded stat data.
> 
> perf top:
> 
>   He Kuang:
> 
>   - Fix wrong hottest instruction highlighted.
> 
> perf python:
> 
>   Arnaldo Carvalho de Melo:
> 
>   - Remove -fstack-clash-protection when building with some clang versions.
> 
> perf ordered_events:
> 
>   Jiri Olsa:
> 
>   - Fix out of buffers crash in ordered_events__free().
> 
> perf cpu_map:
> 
>   Stephane Eranian:
> 
>   - Handle TOPOLOGY headers with no CPU.
> 
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> 
> ----------------------------------------------------------------
> Andi Kleen (1):
>       perf script: Fix crash with printing mixed trace point and other events
> 
> Arnaldo Carvalho de Melo (1):
>       perf python: Remove -fstack-clash-protection when building with some clang versions
> 
> He Kuang (1):
>       perf top: Fix wrong hottest instruction highlighted
> 
> Jiri Olsa (1):
>       perf ordered_events: Fix crash in ordered_events__free
> 
> Stephane Eranian (2):
>       perf core: Fix perf_proc_update_handler() bug
>       perf tools: Handle TOPOLOGY headers with no CPU
> 
> Tony Jones (1):
>       perf script: Fix crash when processing recorded stat data
> 
>  kernel/events/core.c              | 14 +++++++-------
>  tools/perf/builtin-script.c       |  9 +++------
>  tools/perf/ui/browsers/annotate.c | 16 ++++++++++------
>  tools/perf/util/cpumap.c          | 11 +++++++++--
>  tools/perf/util/ordered-events.c  |  6 ++++--
>  tools/perf/util/setup.py          |  2 ++
>  6 files changed, 35 insertions(+), 23 deletions(-)

Pulled, thanks a lot Arnaldo!

	Ingo

  parent reply	other threads:[~2019-01-22 11:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21 18:35 [GIT PULL 0/7] perf/urgent fixes Arnaldo Carvalho de Melo
2019-01-21 18:35 ` [PATCH 1/7] perf ordered_events: Fix crash in ordered_events__free Arnaldo Carvalho de Melo
2019-01-21 18:35 ` [PATCH 2/7] perf script: Fix crash with printing mixed trace point and other events Arnaldo Carvalho de Melo
2019-01-21 18:35 ` [PATCH 3/7] perf core: Fix perf_proc_update_handler() bug Arnaldo Carvalho de Melo
2019-01-21 18:35 ` [PATCH 4/7] perf python: Remove -fstack-clash-protection when building with some clang versions Arnaldo Carvalho de Melo
2019-01-21 18:35 ` [PATCH 5/7] perf tools: Handle TOPOLOGY headers with no CPU Arnaldo Carvalho de Melo
2019-01-21 18:35 ` [PATCH 6/7] perf top: Fix wrong hottest instruction highlighted Arnaldo Carvalho de Melo
2019-01-21 18:35 ` [PATCH 7/7] perf script: Fix crash when processing recorded stat data Arnaldo Carvalho de Melo
2019-01-22 11:30 ` Ingo Molnar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-04-19 12:30 [GIT PULL 0/7] perf/urgent fixes Arnaldo Carvalho de Melo
2019-04-19 17:11 ` Ingo Molnar
2019-04-12 14:29 Arnaldo Carvalho de Melo
2019-04-12 16:33 ` Ingo Molnar
2019-04-12 14:22 Arnaldo Carvalho de Melo
2018-11-21 14:24 Arnaldo Carvalho de Melo
2018-11-21 14:58 ` Ingo Molnar
2018-09-12 18:55 Arnaldo Carvalho de Melo
2018-09-12 19:10 ` Ingo Molnar
2018-05-31 10:32 Arnaldo Carvalho de Melo
2018-05-31 10:40 ` Ingo Molnar
2017-09-29 16:00 Arnaldo Carvalho de Melo
2017-09-29 17:33 ` 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=20190122113008.GB113758@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@kernel.org \
    --cc=acme@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=eranian@google.com \
    --cc=hekuang@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=liu.song.a23@gmail.com \
    --cc=ravi.bangoria@linux.ibm.com \
    --cc=tonyj@suse.de \
    --cc=williams@redhat.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;
as well as URLs for NNTP newsgroup(s).