From: Ingo Molnar <mingo@kernel.org>
To: Jiri Olsa <jolsa@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Bernhard Rosenkraenzer <Bernhard.Rosenkranzer@linaro.org>,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
David Ahern <dsahern@gmail.com>,
Dongsheng <yangds.fnst@cn.fujitsu.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Irina Tirdea <irina.tirdea@intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Stephane Eranian <eranian@google.com>
Subject: Re: [GIT PULL 0/6] perf/core improvements and fixes
Date: Mon, 12 May 2014 17:59:03 +0200 [thread overview]
Message-ID: <20140512155903.GA27283@gmail.com> (raw)
In-Reply-To: <1399886833-15472-1-git-send-email-jolsa@kernel.org>
* Jiri Olsa <jolsa@kernel.org> wrote:
> hi Ingo,
> please consider pulling
>
> thanks,
> jirka
>
>
> The following changes since commit 3e46d21285577a8c9e4c37f9b1002e567c440b28:
>
> Merge tag 'perf-core-for-mingo' of git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf into perf/core (2014-05-05 19:37:51 +0200)
>
> are available in the git repository at:
>
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git tags/perf-core-for-mingo
>
> for you to fetch changes up to 13ce34df11833482cd698331fdbb3f8ced06340d:
>
> perf tools: Use tid for finding thread (2014-05-12 11:09:50 +0200)
>
> ----------------------------------------------------------------
> perf/core improvements and fixes:
>
> . Propagate exit status of a command line workload for
> record command (Namhyung Kim)
>
> . Use tid for finding thread (Namhyung Kim)
>
> . Clarify the output of perf sched map plus small sched
> command fixies (Dongsheng Yang)
>
> Signed-off-by: Jiri Olsa <jolsa@kernel.org>
>
> ----------------------------------------------------------------
> Dongsheng (3):
> perf tools: Add missing event for perf sched record.
> perf tools: Adapt the TASK_STATE_TO_CHAR_STR to new value in kernel space.
> perf tools: Clarify the output of perf sched map.
>
> Namhyung Kim (3):
> perf record: Propagate exit status of a command line workload
> perf tools: Get rid of on_exit() feature test
> perf tools: Use tid for finding thread
>
> tools/perf/builtin-inject.c | 2 +-
> tools/perf/builtin-kmem.c | 2 +-
> tools/perf/builtin-record.c | 158 +++++++++---------------
> tools/perf/builtin-sched.c | 38 +++---
> tools/perf/config/Makefile | 8 --
> tools/perf/config/feature-checks/Makefile | 4 -
> tools/perf/config/feature-checks/test-all.c | 5 -
> tools/perf/config/feature-checks/test-on-exit.c | 16 ---
> tools/perf/tests/code-reading.c | 2 +-
> tools/perf/tests/hists_filter.c | 1 +
> tools/perf/tests/hists_link.c | 2 +
> tools/perf/util/build-id.c | 2 +-
> tools/perf/util/event.c | 2 +-
> 13 files changed, 90 insertions(+), 152 deletions(-)
> delete mode 100644 tools/perf/config/feature-checks/test-on-exit.c
Pulled, thanks a lot Jiri!
Ingo
next prev parent reply other threads:[~2014-05-12 15:59 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 9:27 [GIT PULL 0/6] perf/core improvements and fixes Jiri Olsa
2014-05-12 9:27 ` [PATCH 1/6] perf tools: Add missing event for perf sched record Jiri Olsa
2014-05-12 9:27 ` [PATCH 2/6] perf tools: Adapt the TASK_STATE_TO_CHAR_STR to new value in kernel space Jiri Olsa
2014-05-12 9:27 ` [PATCH 3/6] perf tools: Clarify the output of perf sched map Jiri Olsa
2014-05-12 9:27 ` [PATCH 4/6] perf record: Propagate exit status of a command line workload Jiri Olsa
2014-05-12 9:27 ` [PATCH 5/6] perf tools: Get rid of on_exit() feature test Jiri Olsa
2014-05-12 9:27 ` [PATCH 6/6] perf tools: Use tid for finding thread Jiri Olsa
2014-05-12 15:59 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-16 16:09 [GIT PULL 0/6] perf/core improvements and fixes Arnaldo Carvalho de Melo
2017-03-16 16:30 ` Ingo Molnar
2015-08-31 21:36 Arnaldo Carvalho de Melo
2015-09-01 8:26 ` Ingo Molnar
2015-06-03 22:40 Arnaldo Carvalho de Melo
2015-06-04 5:48 ` Ingo Molnar
2015-06-04 6:07 ` Wangnan (F)
2015-06-04 7:21 ` Ingo Molnar
2015-06-04 10:00 ` Wangnan (F)
2015-06-04 12:40 ` Ingo Molnar
2015-06-04 12:58 ` pi3orama
2015-06-04 14:04 ` Ingo Molnar
2015-06-04 16:22 ` Alexei Starovoitov
2015-06-04 21:48 ` Masami Hiramatsu
2015-06-04 22:07 ` Alexei Starovoitov
2015-06-05 6:41 ` Ingo Molnar
2015-06-05 8:53 ` Wangnan (F)
2015-06-05 12:05 ` Ingo Molnar
2015-06-05 14:06 ` Arnaldo Carvalho de Melo
2015-06-07 13:11 ` Ingo Molnar
2015-06-05 13:59 ` Arnaldo Carvalho de Melo
2015-03-31 20:59 Arnaldo Carvalho de Melo
2015-04-01 7:56 ` Ingo Molnar
2015-03-26 15:40 Arnaldo Carvalho de Melo
2015-03-27 7:37 ` Ingo Molnar
2014-04-30 10:11 Jiri Olsa
2014-05-01 6:26 ` Ingo Molnar
2012-10-31 14:48 Arnaldo Carvalho de Melo
2011-04-20 16:23 Arnaldo Carvalho de Melo
2011-04-21 8:58 ` Ingo Molnar
2011-02-16 22:54 Arnaldo Carvalho de Melo
2011-02-17 13:50 ` 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=20140512155903.GA27283@gmail.com \
--to=mingo@kernel.org \
--cc=Bernhard.Rosenkranzer@linaro.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=irina.tirdea@intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=yangds.fnst@cn.fujitsu.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).