| 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, 29 Oct 2012 10:43:57 +0100 From: Stephane Eranian <eranian@...gle.com> To: Andi Kleen <andi@...stfloor.org> Cc: LKML <linux-kernel@...r.kernel.org>, Jiri Olsa <jolsa@...hat.com>, Peter Zijlstra <peterz@...radead.org>, "mingo@...e.hu" <mingo@...e.hu>, Namhyung Kim <namhyung.kim@....com> Subject: Re: [BUG] perf parser: does not support arbitrary new sysfs events On Mon, Oct 29, 2012 at 2:50 AM, Andi Kleen <andi@...stfloor.org> wrote: > Stephane Eranian <eranian@...gle.com> writes: > >> Hi, >> >> The latest round of perf parser changes broke my PEBS-LL patch series >> (at the last minute). For PEBS-LL, I need to add to generic events but I want >> to keep them PMU specific. As such, they need to live in the sysfs events >> subdir: /sys/devices/cpu/events/mem-loads, sys/devices/cpu/events/mem-stores. >> >> Given your latest rounds of sysfs event changes, I had to modify my kernel >> patches to fit those two new events within your perf_pmu_events_attr tables. >> >> But now, when I try to do: >> >> $ perf record -e cpu/mem-loads/ .... > > - is not supported in an event name. I fixed this in my patchkit > Yes, this was indeed the problem. Glad you tracked it down. We need this patch ASAP. > Yes the sysfs stuff in general is quite fragile. > I would say complicated rather than fragile. -- 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