From: Andi Kleen <ak@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, mingo@kernel.org,
eranian@google.com, Vince Weaver <vincent.weaver@maine.edu>,
jolsa@redhat.com
Subject: Re: [PATCH] Add some documentation on the perf sysfs ABI interface
Date: Sun, 14 Sep 2014 08:44:55 -0700 [thread overview]
Message-ID: <20140914154455.GP5387@tassilo.jf.intel.com> (raw)
In-Reply-To: <20140914153407.GA4064@kroah.com>
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@linux.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.
-Andi
next prev parent reply other threads:[~2014-09-14 15:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 22:34 [PATCH] Add some documentation on the perf sysfs ABI interface Andi Kleen
2014-09-14 9:30 ` Peter Zijlstra
2014-09-14 15:34 ` Greg KH
2014-09-14 15:44 ` Andi Kleen [this message]
2014-09-14 15:53 ` Greg KH
2014-09-14 13:23 ` Jiri Olsa
-- strict thread matches above, loose matches on Subject: below --
2014-09-15 22:47 Andi Kleen
2014-09-09 17:32 Andi Kleen
2014-09-09 19:01 ` Stephane Eranian
2014-09-09 20:11 ` Andi Kleen
2014-09-09 20:57 ` Randy Dunlap
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=20140914154455.GP5387@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=vincent.weaver@maine.edu \
/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