From: Ingo Molnar <mingo@elte.hu>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [GIT PULL] perf and breakpoints updates
Date: Mon, 3 May 2010 08:50:32 +0200 [thread overview]
Message-ID: <20100503065032.GC15241@elte.hu> (raw)
In-Reply-To: <1272682436-10682-1-git-send-regression-fweisbec@gmail.com>
* Frederic Weisbecker <fweisbec@gmail.com> wrote:
> Ingo,
>
> Please pull the perf/core branch that can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
> perf/core
>
> Thanks,
> Frederic
> ---
>
> Frederic Weisbecker (8):
> perf: Remove leftover useless options to record trace events from scripts
> perf: Fix warning while reading ring buffer headers
> hw-breakpoints: Tag ptrace breakpoint as exclude_kernel
> hw-breakpoints: Check disabled breakpoints again
> hw-breakpoints: Change/Enforce some breakpoints policies
> hw-breakpoints: Separate constraint space for data and instruction breakpoints
> hw-breakpoints: Handle breakpoint weight in allocation constraints
> hw-breakpoints: Get the number of available registers on boot dynamically
>
>
> arch/Kconfig | 11 +
> arch/sh/Kconfig | 1 +
> arch/sh/include/asm/hw_breakpoint.h | 10 +-
> arch/sh/kernel/hw_breakpoint.c | 34 +---
> arch/sh/kernel/ptrace_32.c | 2 +-
> arch/x86/Kconfig | 1 +
> arch/x86/include/asm/hw_breakpoint.h | 10 +-
> arch/x86/kernel/hw_breakpoint.c | 41 +----
> arch/x86/kernel/ptrace.c | 2 +-
> include/linux/hw_breakpoint.h | 25 +++-
> kernel/hw_breakpoint.c | 196 +++++++++++++++-----
> kernel/trace/trace_ksym.c | 26 +--
> tools/perf/Documentation/perf-trace-perl.txt | 6 +-
> tools/perf/Documentation/perf-trace-python.txt | 10 +-
> .../perf/scripts/perl/bin/check-perf-trace-record | 2 +-
> tools/perf/scripts/perl/bin/failed-syscalls-record | 2 +-
> tools/perf/scripts/perl/bin/rw-by-file-record | 2 +-
> tools/perf/scripts/perl/bin/rw-by-pid-record | 2 +-
> tools/perf/scripts/perl/bin/rwtop-record | 2 +-
> tools/perf/scripts/perl/bin/wakeup-latency-record | 2 +-
> tools/perf/scripts/perl/bin/workqueue-stats-record | 2 +-
> .../python/bin/failed-syscalls-by-pid-record | 2 +-
> tools/perf/scripts/python/bin/sctop-record | 2 +-
> .../python/bin/syscall-counts-by-pid-record | 2 +-
> .../perf/scripts/python/bin/syscall-counts-record | 2 +-
> tools/perf/util/trace-event-parse.c | 89 ---------
> tools/perf/util/trace-event-read.c | 12 +-
> tools/perf/util/trace-event.h | 1 -
> 28 files changed, 243 insertions(+), 256 deletions(-)
Pulled, thanks a lot Frederic!
Ingo
next prev parent reply other threads:[~2010-05-03 6:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-01 2:53 Frederic Weisbecker
2010-05-01 2:53 ` [PATCH 1/8] perf: Remove leftover useless options to record trace events from scripts Frederic Weisbecker
2010-05-01 2:53 ` [PATCH 2/8] perf: Fix warning while reading ring buffer headers Frederic Weisbecker
2010-05-01 2:53 ` [PATCH 3/8] hw-breakpoints: Tag ptrace breakpoint as exclude_kernel Frederic Weisbecker
2010-05-01 2:53 ` [PATCH 4/8] hw-breakpoints: Check disabled breakpoints again Frederic Weisbecker
2010-05-01 2:53 ` [PATCH 5/8] hw-breakpoints: Change/Enforce some breakpoints policies Frederic Weisbecker
2010-05-01 2:53 ` [PATCH 6/8] hw-breakpoints: Separate constraint space for data and instruction breakpoints Frederic Weisbecker
2010-05-01 2:53 ` [PATCH 7/8] hw-breakpoints: Handle breakpoint weight in allocation constraints Frederic Weisbecker
2010-05-01 2:53 ` [PATCH 8/8] hw-breakpoints: Get the number of available registers on boot dynamically Frederic Weisbecker
2010-05-03 6:50 ` Ingo Molnar [this message]
2010-05-03 7:00 ` [GIT PULL] perf and breakpoints updates Ingo Molnar
2010-05-03 13:39 ` Frederic Weisbecker
2010-05-04 8:30 ` [tip:perf/core] hw_breakpoints: Fix percpu build failure tip-bot for Frederic Weisbecker
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=20100503065032.GC15241@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=rostedt@goodmis.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