From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
"K . Prasad" <prasad@linux.vnet.ibm.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>,
Tejun Heo <tj@kernel.org>
Subject: [GIT PULL] Perf updates
Date: Sat, 27 Feb 2010 19:25:28 +0100 [thread overview]
Message-ID: <1267295133-6320-1-git-send-regression-fweisbec@gmail.com> (raw)
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 (3):
perf lock: Drop the buffers multiplexing dependency
perf: Remove pointless breakpoint union
x86/hw-breakpoints: Remove the name field
Hitoshi Mitake (1):
perf lock: Fix and add misc documentally things
Tejun Heo (1):
percpu: Add __percpu sparse annotations to hw_breakpoint
arch/x86/include/asm/hw_breakpoint.h | 1 -
arch/x86/kernel/hw_breakpoint.c | 7 --
include/linux/hw_breakpoint.h | 8 +-
include/linux/perf_event.h | 5 +-
kernel/hw_breakpoint.c | 10 +-
lib/Kconfig.debug | 8 ++
samples/hw_breakpoint/data_breakpoint.c | 6 +-
tools/perf/Documentation/perf-lock.txt | 29 ++++++
tools/perf/builtin-lock.c | 148 ++++++++++++++++++++++++++++++-
tools/perf/command-list.txt | 1 +
10 files changed, 198 insertions(+), 25 deletions(-)
next reply other threads:[~2010-02-27 18:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 18:25 Frederic Weisbecker [this message]
2010-02-27 18:25 ` [PATCH 1/5] percpu: Add __percpu sparse annotations to hw_breakpoint Frederic Weisbecker
2010-02-27 18:25 ` [PATCH 2/5] perf lock: Fix and add misc documentally things Frederic Weisbecker
2010-02-27 18:25 ` [PATCH 3/5] perf lock: Drop the buffers multiplexing dependency Frederic Weisbecker
2010-02-27 18:25 ` [PATCH 4/5] perf: Remove pointless breakpoint union Frederic Weisbecker
2010-02-27 18:25 ` [PATCH 5/5] x86/hw-breakpoints: Remove the name field Frederic Weisbecker
-- strict thread matches above, loose matches on Subject: below --
2019-09-26 20:06 [GIT PULL] perf updates Ingo Molnar
2019-09-26 23:00 ` pr-tracker-bot
2016-08-06 6:05 Ingo Molnar
2016-05-25 20:18 Ingo Molnar
2015-07-04 11:25 Ingo Molnar
2015-04-18 15:22 Ingo Molnar
2013-11-13 20:58 Ingo Molnar
2012-05-23 19:01 Ingo Molnar
2011-02-26 15:11 [PATCH v2] perf: Fix undefined PyVarObject_HEAD_INIT in python 2.5 Frederic Weisbecker
2011-03-04 0:38 ` [GIT PULL] perf updates Frederic Weisbecker
2011-03-04 7:10 ` Ingo Molnar
2010-06-08 20:13 Frederic Weisbecker
2010-06-08 21:13 ` Ingo Molnar
2010-05-25 13:45 Frederic Weisbecker
2010-05-09 20:43 Frederic Weisbecker
2010-05-10 5:10 ` Frederic Weisbecker
2010-05-10 6:46 ` Ingo Molnar
2010-04-14 15:59 Frederic Weisbecker
2010-04-04 14:36 Frederic Weisbecker
2010-04-04 14:42 ` Frederic Weisbecker
2010-04-04 19:02 ` Ingo Molnar
2010-04-05 9:56 ` Hitoshi Mitake
2010-03-05 21:55 Frederic Weisbecker
2010-03-10 14:28 ` Ingo Molnar
2010-03-03 6:54 Frederic Weisbecker
2009-12-14 16:24 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=1267295133-6320-1-git-send-regression-fweisbec@gmail.com \
--to=fweisbec@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mitake@dcl.info.waseda.ac.jp \
--cc=paulus@samba.org \
--cc=prasad@linux.vnet.ibm.com \
--cc=tj@kernel.org \
/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).