[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.10.1309121515440.10687@vincent-weaver-1.um.maine.edu>
Date: Thu, 12 Sep 2013 15:35:52 -0400 (EDT)
From: Vince Weaver <vincent.weaver@...ne.edu>
To: Ingo Molnar <mingo@...nel.org>
cc: Andi Kleen <andi@...stfloor.org>, Andi Kleen <ak@...ux.intel.com>,
acme@...radead.org, linux-kernel@...r.kernel.org,
Peter Zijlstra <peterz@...radead.org>,
Stephane Eranian <eranian@...gle.com>,
torvalds@...ux-foundation.org, trinity@...r.kernel.org,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Thomas Gleixner <tglx@...utronix.de>,
Frédéric Weisbecker <fweisbec@...il.com>,
Jiri Olsa <jolsa@...hat.com>,
Namhyung Kim <namhyung@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH 1/2] tools, perf: Add a precise event qualifier v2
On Thu, 12 Sep 2013, Ingo Molnar wrote:
> * Andi Kleen <andi@...stfloor.org> wrote:
>
> > On Tue, Jul 23, 2013 at 05:27:43PM -0400, Vince Weaver wrote:
> > >
> > > I hate having to justify why breaking the ABI is unacceptable.
> >
> > Well it's a testing ABI, so we can do changes to it.
> >
> > I hope you're not suggesting that perf cannot be extended anymore.
>
> It obviously should remain extensible, limiting it to 'config' is rather
> stupid. If a parser sees something it cannot parse it should ignore that
> event.
Well
Documentation/ABI/testing/sysfs-bus-event_source-devices-events
implies that you won't find field names that aren't in a format file, and
Documentation/ABI/testing/sysfs-bus-event_source-devices-format
specifies that only "config" fields will appear there.
So if this will be changing you might want to update the documentation, or
just remove it altogether because it is getting increasingly inaccurate.
I've tried getting this documentation updated
( https://lkml.org/lkml/2013/7/25/2 )
but the patches have been ignored.
In any case, I notice perf also uses the "open" syscall, so I look forward
to your eventual creation of
/sys/bus/open/file_permissions/*
$ cat /sys/bus/open/file_permissions/write
flags=0101,mode=0666
Because what every system call needs is some sort of tree under sysfs
exporting various common settings in unswappable kernel memory that
require a complex LEX/YACC parser to interpret.
That's much simpler than using a library, or having a user looking
things up in a manpage and placing a few comments in their code.
Vince
--
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