lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 24 Feb 2014 10:46:35 +0000 From: Will Deacon <will.deacon@....com> To: Vince Weaver <vincent.weaver@...ne.edu> Cc: Peter Zijlstra <peterz@...radead.org>, Chad Paradis <chad.paradis@...t.maine.edu>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Paul Mackerras <paulus@...ba.org>, Ingo Molnar <mingo@...hat.com>, Arnaldo Carvalho de Melo <acme@...stprotocols.net>, Stephane Eranian <eranian@...il.com> Subject: Re: [patch/rfc] perf on raspberry-pi without overflow interrupt 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists