public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lin Ming <ming.m.lin@intel.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: mingo@elte.hu, Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Paul Mackerras <paulus@samba.org>,
	Stephane Eranian <eranian@google.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>
Subject: [RFC] perf: EBNF for event syntax
Date: Wed, 23 Mar 2011 11:36:56 +0800	[thread overview]
Message-ID: <1300851416.31224.58.camel@minggr.sh.intel.com> (raw)

Hi, all

On Thu, Mar 17, 2011 at 2:02 AM, Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> How about we start writing proper EBNF syntax rules for this stuff, its
> getting seriously out of hand.
http://marc.info/?l=linux-kernel&m=130029871318866&w=2

As Peter suggested, I wrote a simple EBNF for event syntax, as below.
My first plan is to pass in extra config value for some events,
for example, offcore response and load latency.

perf record -e r100b(0004):p

As above, the extra config value 0004 is passed in the parentheses.

The EBNF
========

EventList		:=	Event [',' EventList]
Event			:= 	HardwareEvent 		|
				RawEvent		|
				SoftwareEvent		|
				TracepointEvent		|
				HardwareBreakpointEvent

HardwareEvent		:=	HardwareEventName [ExtraConfig] [Modifer]
HardwareEventName	:=	'cpu-cycles' | 'cycles' | 'instructions' /* and so on ...*/
ExtraConfig		:=	'(' ConfigValue [',' ConfigValue] ')'
ConfigValue		:=	HexNumber

RawEvent		:=	RawSeperator RawCode [ExtraConfig] [Modifer]
RawSeperator		:=	'r'
RawCode			:=	HexNumber

SoftwareEvent		:=	SoftwareEventName
SoftwareEventName	:=	'cpu-clock' | 'task-clock' | 'faults' /* and so on ...*/

TracepointEvent		:=	SubsystemName ':' TracepointName
SubsystemName		:=	/* All AsciiString except the pre-defined hardware/software/cache events name and BreakpointSeparator */
TracepointName		:=	'*' | AsciiString

HardwareBreakpointEvent	:=	BreakpointSeparator BreakpointAddress [':' AccessType]
BreakpointSeparator	:=	'mem:'
BreakpointAddress	:=	HexNumber
AccessType		:=	'r' | 'w' | 'x'

Modifier		:= 	ModifierSperator ModifierList
ModifierSperator	:= 	':'
ModifierList		:= 	ModifierItem ModifierList
ModifierItem		:= 	{PreciseModifer} | kernelModifer | UserModifer | HypervisorModifer
PreciseModifer		:= 	'p' /* Can be multiple PreciseModifers */
kernelModifer		:= 	'k'
UserModifer		:= 	'u'
HypervisorModifer	:= 	'h'


Some valid examples
===================
Hardware events with modifiers,
cycles:pk,instructions:u

Raw event with extra config values and/or modifiers,
r0110(40A0):pu
r0110(40A0,40A1):k

Software event,
cpu-clock,faults

Hardware breakpoint events:
mem:400346
mem:800A03:w

Some invalid examples
=====================
r0110(40A0,40A1,40A2), invalid, only 2 extra config values are allowed
cpu-clock:p, invalid, software event does not have precise modifier


Any comments?

Thanks,
Lin Ming



             reply	other threads:[~2011-03-23  3:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23  3:36 Lin Ming [this message]
2011-03-25 11:07 ` [RFC] perf: EBNF for event syntax Peter Zijlstra
2011-03-25 13:35   ` Lin Ming
2011-03-25 14:17     ` Peter Zijlstra
2011-03-26 20:48       ` Ulrich Drepper
2011-03-28  5:40   ` Masami Hiramatsu
2011-03-28  7:58     ` Peter Zijlstra
2011-03-28  8:52       ` Matt Fleming
2011-03-28 10:12       ` Masami Hiramatsu

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=1300851416.31224.58.camel@minggr.sh.intel.com \
    --to=ming.m.lin@intel.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@elte.hu \
    --cc=mitake@dcl.info.waseda.ac.jp \
    --cc=paulus@samba.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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