public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Paul Mackerras <paulus@samba.org>
Subject: [GIT PULL v3] perf fixes
Date: Thu, 1 Apr 2010 09:17:49 +0200	[thread overview]
Message-ID: <20100401071742.GB5207@nowhere> (raw)
In-Reply-To: <1270007927-6391-1-git-send-regression-fweisbec@gmail.com>

On Wed, Mar 31, 2010 at 05:58:45AM +0200, Frederic Weisbecker wrote:
> 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


I have updated the tree. There was a leftover patch for perf/core
inside (not listed here). Also, since you've merged linus tree in
perf/urgent lately, I've zapped my merge commit. Other than that,
the three fixes remain.

Thanks.



> 
> 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(-)


  parent reply	other threads:[~2010-04-01  6:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-31  3:58 [GIT PULL v2] perf fixes Frederic Weisbecker
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 ` Frederic Weisbecker [this message]
2010-04-02 17:32   ` [GIT PULL v3] perf fixes Ingo Molnar
2010-04-03 10:38     ` 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=20100401071742.GB5207@nowhere \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox