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: Mon, 24 Feb 2014 10:46:35 +0000 [thread overview]
Message-ID: <20140224104634.GA2553@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1401170041350.4747@vincent-weaver-1.um.maine.edu>
Hi Vince,
On Fri, Jan 17, 2014 at 05:45:04AM +0000, Vince Weaver wrote:
> On Thu, 16 Jan 2014, Peter Zijlstra wrote:
>
> > Yeah I suppose we could do something like that. Maybe something like:
> >
> > # cat /sys/bus/event_source/devices/cpu/flags
> > int precise filter
>
> wouldn't that violate the "one value per file" rule?
>
> I guess we could also stick it in the mmap page somewhere, as tools like
> PAPI already have to check there for things like rdpmc support.
>
>
> Anyway, here's a first pass at a generic fix for this issue. I'm sure the
> code is pretty horrible, I don't usually mess with the perf code at this
> level. I haven't tested yet as it touched enough files that the rasp-pi
> is going to take a few hours to finish compiling.
>
> Am I on the right track, or totally off here?
Where did we get to with this? If the generic changes are going to take some
time, I'm happy to take a temporary (non-invasive) fix in the ARM backend while
you sort out the core.
Will
next prev parent reply other threads:[~2014-02-24 10:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 21:28 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 [this message]
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
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=20140224104634.GA2553@mudshark.cambridge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®