public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello•nl>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: linuxppc-dev@ozlabs•org, mingo@elte•hu, paulus@samba•org,
	Anton Blanchard <anton@samba•org>,
	linux-kernel@vger•kernel.org
Subject: Re: [PATCH] powerpc/perf_counter: Add alignment-faults and emulation-faults sw events
Date: Mon, 27 Jul 2009 08:26:02 +0200	[thread overview]
Message-ID: <1248675962.6987.1423.camel@twins> (raw)
In-Reply-To: <1248659272.28464.29.camel@pasglop>

On Mon, 2009-07-27 at 11:47 +1000, Benjamin Herrenschmidt wrote:

> Sounds good.
> 
> BTW. The patch relies on some perctr changes I don't have in my tree
> (PERF_COUNT_SW_ALIGNMENT_FAULTS isn't defined for me)
> 
> Ingo, how do you want to handle that ? Should I wait til round 2 of the
> merge window before putting Anton's patch in or can I merge some of your
> stuff in powerpc-next as pre-reqs ? Or you can just take Anton's patch
> with my:
> 
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel•crashing.org>
> 
> And stick it in your own queue (though pls, give me a pointer to the git
> tree in question so I can verify that I don't get new stuff that
> conflicts before we get to the merge window).

Please send all missing bits to me and I'll stuff it into:

  git://git.kernel.org/pub/scm/linux/kernel/git/peterz/linux-2.6-perf.git perf-master

  parent reply	other threads:[~2009-07-27  6:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06 12:18 [PATCH] powerpc/perf_counter: Add alignment-faults and emulation-faults sw events Anton Blanchard
2009-07-27  1:47 ` Benjamin Herrenschmidt
2009-07-27  1:51   ` Anton Blanchard
2009-07-27  4:57     ` Benjamin Herrenschmidt
2009-07-27  6:26   ` Peter Zijlstra [this message]
2009-07-27  6:27     ` Peter Zijlstra

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=1248675962.6987.1423.camel@twins \
    --to=a.p.zijlstra@chello$(echo .)nl \
    --cc=anton@samba$(echo .)org \
    --cc=benh@kernel$(echo .)crashing.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=mingo@elte$(echo .)hu \
    --cc=paulus@samba$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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