From: Ingo Molnar <mingo@elte.hu>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
linux-kernel@vger.kernel.org, Anton Blanchard <anton@samba.org>
Subject: Re: [GIT PULL] perf_event/tracing/powerpc patches from Anton Blanchard
Date: Sun, 8 Nov 2009 10:35:18 +0100 [thread overview]
Message-ID: <20091108093518.GD21267@elte.hu> (raw)
In-Reply-To: <1256882649.6372.65.camel@pasglop>
* Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> On Thu, 2009-10-29 at 07:55 +0100, Ingo Molnar wrote:
> > * Paul Mackerras <paulus@samba.org> wrote:
> >
> > > Here is a series of patches from Anton Blanchard that implement some
> > > nice tracing and perf_event features on powerpc. One of them is
> > > generic perf_event stuff (adding software events for alignment faults
> > > and instruction emulation faults).
> > >
> > > Since this touches the perf_event and tracing subsystems as well as
> > > the powerpc architecture code, I think the best way forward is for
> > > both Ingo and Ben to pull it into their trees. I have based it on the
> > > most recent point in Linus' tree that Ingo had pulled into his perf
> > > branches (as of yesterday or so).
> >
> > The generic perf bits look good to me - can pull it if Ben OKs the
> > PowerPC bits.
>
> Yup. Just went through all of them, they look fine. I also test built on
> a number of default configs and it seems to pass.
Pulled into tip:perf/powerpc (will keep it in a separate branch for a
few days then it can go into perf/core), thanks guys!
Ingo
prev parent reply other threads:[~2009-11-08 9:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 0:56 [GIT PULL] perf_event/tracing/powerpc patches from Anton Blanchard Paul Mackerras
2009-10-29 1:44 ` Benjamin Herrenschmidt
2009-10-29 2:43 ` Paul Mackerras
2009-10-29 6:55 ` Ingo Molnar
2009-10-30 6:04 ` Benjamin Herrenschmidt
2009-11-08 9:35 ` Ingo Molnar [this message]
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=20091108093518.GD21267@elte.hu \
--to=mingo@elte.hu \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.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).