From: Will Deacon <will.deacon@arm.com>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: Peter Zijlstra <peterz@infradead.org>,
Chad Paradis <chad.paradis@umit.maine.edu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Stephane Eranian <eranian@gmail.com>
Subject: Re: [patch/rfc] perf on raspberry-pi without overflow interrupt
Date: Wed, 7 May 2014 22:23:54 +0100 [thread overview]
Message-ID: <20140507212354.GC5311@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1405071719430.7020@vincent-weaver-1.umelst.maine.edu>
On Wed, May 07, 2014 at 10:21:52PM +0100, Vince Weaver wrote:
> On Wed, 7 May 2014, Will Deacon wrote:
>
> > > OK, let me revisit the patches. The last set of generic ones I sent out
> > > actually was broken on ARM and I've been meaning to straighten things out
> > > and send a proper follow up patch set but got distracted by other perf
> > > related issues.
> >
> > Any luck with this? I just got (another) report of a PMU with borked
> > interrupts, so a fix would be great if you've got one.
>
> Let me see if I can get a final patch out for that.
>
> I've been working on it off and on, the problem is that the patch that
> enables things on the Raspberry Pi somehow breaks sampled events on my
> pandaboard.
>
> Let me compile up some new kernels and do some more testing and hopefully
> get this sorted out this week.
Cheers Vince, much appreciated. I can help test if you need it (my broken
boards will come in useful at last!)
Will
next prev parent reply other threads:[~2014-05-07 21:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 21:28 [patch/rfc] perf on raspberry-pi without overflow interrupt Vince Weaver
2014-01-08 22:23 ` Stephane Eranian
2014-01-08 22:53 ` Peter Zijlstra
2014-01-09 3:47 ` Vince Weaver
2014-01-09 10:19 ` Will Deacon
2014-01-10 4:08 ` Vince Weaver
2014-01-10 9:40 ` Peter Zijlstra
2014-01-14 4:55 ` Vince Weaver
2014-01-14 10:57 ` Peter Zijlstra
2014-01-16 17:13 ` Vince Weaver
2014-01-16 17:31 ` Peter Zijlstra
2014-01-17 5:45 ` Vince Weaver
2014-02-24 10:46 ` Will Deacon
2014-02-24 15:37 ` Vince Weaver
2014-05-07 17:29 ` Will Deacon
2014-05-07 21:21 ` Vince Weaver
2014-05-07 21:23 ` Will Deacon [this message]
2014-01-10 10:08 ` Will Deacon
2014-01-10 10:43 ` Stephane Eranian
2014-01-10 13:54 ` Vince Weaver
2014-01-14 4:42 ` Vince Weaver
2014-01-15 18:38 ` Will Deacon
2014-01-16 16:13 ` Vince Weaver
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=20140507212354.GC5311@arm.com \
--to=will.deacon@arm.com \
--cc=acme@ghostprotocols.net \
--cc=chad.paradis@umit.maine.edu \
--cc=eranian@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=vincent.weaver@maine.edu \
/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.