From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
David Ahern <david.ahern@oracle.com>,
Davidlohr Bueso <dbueso@suse.de>, He Kuang <hekuang@huawei.com>,
Javi Merino <javi.merino@arm.com>, Jiri Olsa <jolsa@redhat.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Mel Gorman <mgorman@suse.de>, Namhyung Kim <namhyung@kernel.org>,
Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Petr Holasek <pholasek@redhat.com>,
Wang Nan <wangnan0@huawei.com>, Zefan Li <lizefan@huawei.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: [GIT PULL 0/7] perf/urgent fixes
Date: Mon, 27 Apr 2015 14:04:02 -0300 [thread overview]
Message-ID: <1430154249-28268-1-git-send-email-acme@kernel.org> (raw)
Hi Ingo,
Please consider pulling, this is on top of my previous 'perf-urgent-for-mingo'
pull request.
- Arnaldo
The following changes since commit de28c15daf60e9625bece22f13a091fac8d05f1d:
tools lib api: Undefine _FORTIFY_SOURCE before setting it (2015-04-23 17:08:23 -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-2
for you to fetch changes up to 1d90a685eb75a56648d7dd22c704a1a6da516de9:
perf bench numa: Fix immediate meeting of convergence condition (2015-04-27 13:57:50 -0300)
----------------------------------------------------------------
perf/urgent fixes:
User visible:
. Fix a segfault in 'perf top' when kernel map is restricted (Wang Nan)
. Fix hung wakeup tasks after requeueing in 'perf bench futex' (Davidlohr Bueso)
. Fix bug in perf probe global variables handling, missing curly braces on
an if body (He Kuang)
. 'perf bench numa' fixes (command line help/handling, etc) (Petr Holasek)
Build fixes:
. 'perf kmem' on RHEL6/OL6 (David Ahern)
. libtraceevent on 32-bit arch (Namhyung Kim)
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
----------------------------------------------------------------
David Ahern (1):
perf kmem: Fix compiles on RHEL6/OL6
Davidlohr Bueso (1):
perf bench futex: Fix hung wakeup tasks after requeueing
He Kuang (1):
perf probe: Fix bug with global variables handling
Namhyung Kim (1):
tools lib traceevent: Fix build failure on 32-bit arch
Petr Holasek (2):
perf bench numa: Fixes of --quiet argument
perf bench numa: Fix immediate meeting of convergence condition
Wang Nan (1):
perf top: Fix a segfault when kernel map is restricted.
tools/lib/traceevent/event-parse.c | 2 +-
tools/perf/bench/futex-requeue.c | 15 ++++++-----
tools/perf/bench/numa.c | 12 +++++++--
tools/perf/builtin-kmem.c | 54 +++++++++++++++++++-------------------
tools/perf/builtin-top.c | 2 +-
tools/perf/util/probe-finder.c | 4 ++-
6 files changed, 50 insertions(+), 39 deletions(-)
next reply other threads:[~2015-04-27 17:04 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 17:04 Arnaldo Carvalho de Melo [this message]
2015-04-27 17:04 ` [PATCH 1/7] perf kmem: Fix compiles on RHEL6/OL6 Arnaldo Carvalho de Melo
2015-04-27 17:04 ` [PATCH 2/7] tools lib traceevent: Fix build failure on 32-bit arch Arnaldo Carvalho de Melo
2015-04-27 17:04 ` [PATCH 3/7] perf top: Fix a segfault when kernel map is restricted Arnaldo Carvalho de Melo
2015-04-27 17:04 ` [PATCH 4/7] perf probe: Fix bug with global variables handling Arnaldo Carvalho de Melo
2015-04-27 17:04 ` [PATCH 5/7] perf bench futex: Fix hung wakeup tasks after requeueing Arnaldo Carvalho de Melo
2015-04-27 17:04 ` [PATCH 6/7] perf bench numa: Fixes of --quiet argument Arnaldo Carvalho de Melo
2015-04-27 17:04 ` [PATCH 7/7] perf bench numa: Fix immediate meeting of convergence condition Arnaldo Carvalho de Melo
2015-05-01 6:32 ` [GIT PULL 0/7] perf/urgent fixes Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2019-04-19 12:30 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
2019-01-21 18:35 Arnaldo Carvalho de Melo
2019-01-22 11:30 ` Ingo Molnar
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 18:55 ` Arnaldo Carvalho de Melo
2018-09-12 19:10 ` Ingo Molnar
2018-09-12 19:10 ` Ingo Molnar
2018-05-31 10:32 Arnaldo Carvalho de Melo
2018-05-31 10:32 ` Arnaldo Carvalho de Melo
2018-05-31 10:32 ` Arnaldo Carvalho de Melo
2018-05-31 10:32 ` Arnaldo Carvalho de Melo
2018-05-31 10:32 ` Arnaldo Carvalho de Melo
2018-05-31 10:40 ` Ingo Molnar
2018-05-31 10:40 ` Ingo Molnar
2018-05-31 10:40 ` Ingo Molnar
2018-05-31 10:40 ` Ingo Molnar
2018-05-31 10:40 ` Ingo Molnar
2017-09-29 16:00 Arnaldo Carvalho de Melo
2017-09-29 16:00 ` Arnaldo Carvalho de Melo
2017-09-29 17:33 ` Ingo Molnar
2017-09-29 17:33 ` Ingo Molnar
2015-02-25 21:05 Arnaldo Carvalho de Melo
2014-04-30 15:32 Jiri Olsa
2014-05-01 6:25 ` 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=1430154249-28268-1-git-send-email-acme@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=david.ahern@oracle.com \
--cc=dbueso@suse.de \
--cc=hekuang@huawei.com \
--cc=javi.merino@arm.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=pholasek@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.