From: Frederic Weisbecker <fweisbec@gmail.com>
To: Will Deacon <will.deacon@arm.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Paul Mackerras <paulus@samba.org>,
Stephane Eranian <eranian@google.com>,
Paul Mundt <lethal@linux-sh.org>,
David Miller <davem@davemloft.net>,
Borislav Petkov <bp@amd64.org>
Subject: Re: [RFC PATCH 0/0 v3] callchain fixes and cleanups
Date: Wed, 18 Aug 2010 05:55:09 +0200 [thread overview]
Message-ID: <20100818035507.GE24748@nowhere> (raw)
In-Reply-To: <1282041159.22114.2.camel@e102144-lin.cambridge.arm.com>
On Tue, Aug 17, 2010 at 11:32:39AM +0100, Will Deacon wrote:
> On Mon, 2010-08-16 at 21:48 +0100, Frederic Weisbecker wrote:
> > Hi,
> >
> Hi Frederic,
> >
> > This set factorizes a lot of callchain code and fixes concurrent
> > callchain buffers accesses.
>
> > You can test it by pulling that branch:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
> > perf/callchains
> >
>
> I've tested this on an ARM Cortex-A9 board and it all seems fine [plus
> the code is a lot cleaner!].
>
> Tested-by: Will Deacon <will.deacon@arm.com>
Thanks a lot!
BTW, out of curiosity, do you have NMIs on ARM and do the hardware events
make use of them? Or may be you use FIQ to simulate NMIs?
next prev parent reply other threads:[~2010-08-18 3:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 20:48 [RFC PATCH 0/0 v3] callchain fixes and cleanups Frederic Weisbecker
2010-08-16 20:48 ` [RFC PATCH 1/6] perf: Drop unappropriate tests on arch callchains Frederic Weisbecker
2010-08-16 20:48 ` [RFC PATCH 2/6] perf: Generalize callchain_store() Frederic Weisbecker
2010-08-17 4:37 ` Paul Mackerras
2010-08-16 20:48 ` [RFC PATCH 3/6] perf: Generalize some arch callchain code Frederic Weisbecker
2010-08-17 3:46 ` Paul Mackerras
2010-08-18 3:51 ` Frederic Weisbecker
2010-08-16 20:48 ` [RFC PATCH 4/6] perf: Factorize callchain context handling Frederic Weisbecker
2010-08-17 4:37 ` Paul Mackerras
2010-08-16 20:48 ` [RFC PATCH 5/6] perf: Fix race in callchains Frederic Weisbecker
2010-08-17 1:34 ` [RFC PATCH 5/6 v4] " Frederic Weisbecker
2010-08-17 4:53 ` Paul Mackerras
2010-08-18 3:49 ` Frederic Weisbecker
2010-08-16 20:48 ` [RFC PATCH 6/6] perf: Humanize the number of contexts Frederic Weisbecker
2010-08-17 4:58 ` [RFC PATCH 0/0 v3] callchain fixes and cleanups Borislav Petkov
2010-08-18 3:53 ` Frederic Weisbecker
2010-08-17 10:32 ` Will Deacon
2010-08-18 3:55 ` Frederic Weisbecker [this message]
2010-08-18 9:08 ` Will Deacon
2010-08-18 16:15 ` 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=20100818035507.GE24748@nowhere \
--to=fweisbec@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=bp@amd64.org \
--cc=davem@davemloft.net \
--cc=eranian@google.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=will.deacon@arm.com \
/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