[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140914155320.GA4804@kroah.com>
Date: Sun, 14 Sep 2014 08:53:20 -0700
From: Greg KH <gregkh@...uxfoundation.org>
To: Andi Kleen <ak@...ux.intel.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
mingo@...nel.org, eranian@...gle.com,
Vince Weaver <vincent.weaver@...ne.edu>, jolsa@...hat.com
Subject: Re: [PATCH] Add some documentation on the perf sysfs ABI interface
On Sun, Sep 14, 2014 at 08:44:55AM -0700, Andi Kleen wrote:
> On Sun, Sep 14, 2014 at 08:34:07AM -0700, Greg KH wrote:
> > On Sun, Sep 14, 2014 at 11:30:33AM +0200, Peter Zijlstra wrote:
> > > On Fri, Sep 12, 2014 at 03:34:19PM -0700, Andi Kleen wrote:
> > > > From: Andi Kleen <ak@...ux.intel.com>
> > > >
> > > > Initial attempt of documenting the perf sysfs interface as
> > > > an ABI. I also added some additional pointers hopefully useful
> > > > to the users. Comments welcome.
> > >
> > > My only worry is that its a little x86 centric and I'm not sure if that
> > > is acceptable with the sysfs crowd, Greg?
> >
> > Does this document what you have today? If so, that's fine, and good to
> > do.
> >
> > Or, is this a proposed interface that is different per architecture in
> > subtle non-portable ways? If so, probably not :)
>
> Each architecture describes its own fields in a generic format that
> can be handled by a generic parser. The generic description is documented.
>
> However I also described the x86 specific attributes.
>
> This is all implemented today.
Ok, as long as things are "one value per file", I have no objection,
thanks for the documentation.
greg k-h
--
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