From: Ingo Molnar <mingo@kernel.org>
To: Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jiri Olsa <jolsa@redhat.com>, Mike Galbraith <efault@gmx.de>,
Namhyung Kim <namhyung@gmail.com>,
Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <peterz@infradead.org>,
Stephane Eranian <eranian@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
arnaldo.melo@gmail.com,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [GIT PULL 0/3] perf/core trace improvements
Date: Fri, 26 Oct 2012 10:32:38 +0200 [thread overview]
Message-ID: <20121026083238.GB27378@gmail.com> (raw)
In-Reply-To: <1351194465-29083-1-git-send-email-acme@infradead.org>
* Arnaldo Carvalho de Melo <acme@infradead.org> wrote:
> Hi Ingo,
>
> Please consider pulling, got sidetracked today with some other stuff,
> but made progress on reviewing the group patches from Namhyung that Jiri uses
> for that PERF_SAMPLE_READ patchset.
>
> - Arnaldo
>
> The following changes since commit 6ca2a9c6543dd1a307c0250991d4de93550209ce:
>
> Merge tag 'perf-core-for-mingo' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/core (2012-10-25 09:42:03 +0200)
>
> are available in the git repository at:
>
>
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux tags/perf-core-for-mingo
>
> for you to fetch changes up to 1302d88e66f12a7b46a5598e641d93f0713007e0:
>
> perf trace: Use sched:sched_stat_runtime to provide a thread summary (2012-10-25 10:57:43 -0200)
>
> ----------------------------------------------------------------
> perf/core trace improvements:
>
> . Don't stop synthesizing threads when one vanishes, this is for
> the existing threads when we start a tool like trace.
>
> . Use sched:sched_stat_runtime to provide a thread summary, this
> produces the same output as the 'trace summary' subcommand of
> tglx's original "trace" tool.
>
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
>
> ----------------------------------------------------------------
> Arnaldo Carvalho de Melo (3):
> perf tools: Don't stop synthesizing threads when one vanishes
> perf trace: Count number of events for each thread and globally
> perf trace: Use sched:sched_stat_runtime to provide a thread summary
>
> tools/perf/Documentation/perf-trace.txt | 3 +
> tools/perf/builtin-trace.c | 108 +++++++++++++++++++++++++++++--
> tools/perf/util/event.c | 13 ++--
> 3 files changed, 110 insertions(+), 14 deletions(-)
Pulled, thanks a lot Arnaldo!
Ingo
prev parent reply other threads:[~2012-10-26 8:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 19:47 Arnaldo Carvalho de Melo
2012-10-25 19:47 ` [PATCH 1/3] perf tools: Don't stop synthesizing threads when one vanishes Arnaldo Carvalho de Melo
2012-10-25 19:47 ` [PATCH 2/3] perf trace: Count number of events for each thread and globally Arnaldo Carvalho de Melo
2012-10-25 19:47 ` [PATCH 3/3] perf trace: Use sched:sched_stat_runtime to provide a thread summary Arnaldo Carvalho de Melo
2012-10-26 8:32 ` Ingo Molnar [this message]
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=20121026083238.GB27378@gmail.com \
--to=mingo@kernel.org \
--cc=acme@infradead.org \
--cc=acme@redhat.com \
--cc=arnaldo.melo@gmail.com \
--cc=dsahern@gmail.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@gmail.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome