linux-kernel - Re: [RFCv3 0/9] perf tool: parser generator for events parsing

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1327422364.2446.75.camel@twins>
Date:	Tue, 24 Jan 2012 17:26:04 +0100
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Jiri Olsa <jolsa@...hat.com>
Cc:	acme@...hat.com, mingo@...e.hu, paulus@...ba.org,
	cjashfor@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org,
	Greg KH <greg@...ah.com>
Subject: Re: [RFCv3 0/9] perf tool: parser generator for events parsing

On Mon, 2012-01-16 at 13:31 +0100, Jiri Olsa wrote:
> Here's new version of event parsing patchset. To summarize:
>  - adding event parser bison/flex generator
>  - the event syntax stays as it was
>  - adding event format file sysfs attribute
>    for pmu device

Added Greg to CC, please also see: https://lkml.org/lkml/2012/1/16/148

Right, lets hope we can convince the sysfs people that a few lines are
ok.. if not we need to find another way to represent all this muck, one
alternative is exploding the whole thing into a sysfs hierarchy like:


format/event: config:0-7
...

format/config: config:0-63
format/config1: config1:0-63
format/config2: config2:0-63

that will of course consume loads more resources but if that's what it
takes :-(

>  - adding new syntax to specify raw events based
>    on the sysfs pmu's format attribute
>    eg. "cpu/config=1,config1=2,config2=3/u" 

fair enough, so we have the attributes from the $FORMAT thingy and (for
now) one hardcoded 'period' thing.

Should we worry about namespace collisions for the built-in vs format
provided names?

I suppose that once we get all this in (and it looks good from my pov),
we can start thinking about doing things like:

events/cycles: event=0x3c

Which together with:

format/event: config:0-7

would allow us to write something like:

cpu/event=cycles/u


--
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/