From: Frederic Weisbecker <fweisbec@gmail.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>, Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Paul Mackerras <paulus@samba.org>
Subject: [GIT PULL v2] perf fixes
Date: Wed, 31 Mar 2010 05:58:45 +0200 [thread overview]
Message-ID: <1270007927-6391-1-git-send-regression-fweisbec@gmail.com> (raw)
Ingo,
Please pull the perf/urgent branch that can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
perf/urgent
It fixes the conflict against latest linus's tree that raised
build errors (you can find a merge commit inside).
I am not yet totally sure about Peter's opinion concerning
the context switch event that is now captured from the kernel.
Our latest discussion on the strict exclude_kernel meaning
seems in favour of this change but I'd prefer to wait for his
final approval before you pull this.
(I'm not reposting the alignment fix as it is unchanged)
Thanks,
Frederic
---
Frederic Weisbecker (2):
perf: Correctly align perf event tracing buffer
perf: Use hot regs with software sched switch/migrate events
Jason Wessel (1):
x86,kgdb: Always initialize the hw breakpoint attribute
arch/x86/kernel/cpu/perf_event.c | 2 --
arch/x86/kernel/kgdb.c | 2 +-
include/linux/perf_event.h | 21 ++++++++++++++-------
kernel/perf_event.c | 4 +---
kernel/trace/trace_event_perf.c | 11 +++++++++--
5 files changed, 25 insertions(+), 15 deletions(-)
next reply other threads:[~2010-03-31 3:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 3:58 Frederic Weisbecker [this message]
2010-03-31 3:58 ` [PATCH 1/2 v2] perf: Use hot regs with software sched switch/migrate events Frederic Weisbecker
2010-03-31 3:58 ` [PATCH 2/2] x86,kgdb: Always initialize the hw breakpoint attribute Frederic Weisbecker
2010-04-01 7:17 ` [GIT PULL v3] perf fixes Frederic Weisbecker
2010-04-02 17:32 ` Ingo Molnar
2010-04-03 10:38 ` Frederic Weisbecker
-- strict thread matches above, loose matches on Subject: below --
2010-06-02 12:28 [GIT PULL] " Ingo Molnar
2010-06-03 18:39 ` [GIT PULL, v2] " Ingo Molnar
2010-03-16 16:06 [GIT PULL] " Ingo Molnar
2010-03-17 11:33 ` [GIT PULL, v2] " Ingo Molnar
2009-12-31 12:00 [GIT PULL] " Ingo Molnar
2009-12-31 12:39 ` [GIT PULL, v2] " 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=1270007927-6391-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=paulus@samba.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 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.