From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752702AbaINPyK (ORCPT ); Sun, 14 Sep 2014 11:54:10 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:42307 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752657AbaINPyJ (ORCPT ); Sun, 14 Sep 2014 11:54:09 -0400 Date: Sun, 14 Sep 2014 08:53:20 -0700 From: Greg KH To: Andi Kleen Cc: Peter Zijlstra , Andi Kleen , linux-kernel@vger.kernel.org, mingo@kernel.org, eranian@google.com, Vince Weaver , jolsa@redhat.com Subject: Re: [PATCH] Add some documentation on the perf sysfs ABI interface Message-ID: <20140914155320.GA4804@kroah.com> References: <1410561259-523-1-git-send-email-andi@firstfloor.org> <20140914093033.GR346@worktop.programming.kicks-ass.net> <20140914153407.GA4064@kroah.com> <20140914154455.GP5387@tassilo.jf.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140914154455.GP5387@tassilo.jf.intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > > > > > > > > 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