Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759644Ab1CDOlf (ORCPT ); Fri, 4 Mar 2011 09:41:35 -0500 Received: from mail-bw0-f46.google.com ([209.85.214.46]:58531 "EHLO mail-bw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759294Ab1CDOld (ORCPT ); Fri, 4 Mar 2011 09:41:33 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=iILDNw3YmvFmhfk2DLuFWfukjf/VMcw2GWDKH0JcaMEL3D4txaWf+EfC+Ti6/jCDDg 0W1Mn7gS4PE4R8hsUGW3QjhsblYLVoaeEqb1oMnooRjM+GvQGayKnqXrwF57TZ9naOlX dEuDaG0LY4+kVU7ezoa7u03T/oeHHDWrjKW2c= Date: Fri, 4 Mar 2011 15:41:22 +0100 From: Frederic Weisbecker To: Steven Rostedt Cc: Hitoshi Mitake , Peter Zijlstra , linux-kernel@vger.kernel.org, h.mitake@gmail.com, Paul Mackerras , Ingo Molnar , Arnaldo Carvalho de Melo Subject: Re: [PATCH] perf lock: clean the options for perf record Message-ID: <20110304144119.GE1972@nowhere> References: <4D63D685.2010401@dcl.info.waseda.ac.jp> <1298389415.2217.243.camel@twins> <20110222182206.GB1799@nowhere> <4D648A65.2040107@dcl.info.waseda.ac.jp> <4D667D60.5010903@dcl.info.waseda.ac.jp> <20110224165014.GB1840@nowhere> <4D67E286.8010907@dcl.info.waseda.ac.jp> <4D70B3E1.8020108@dcl.info.waseda.ac.jp> <1299249438.20306.3.camel@gandalf.stny.rr.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1299249438.20306.3.camel@gandalf.stny.rr.com> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1017 Lines: 22 On Fri, Mar 04, 2011 at 09:37:18AM -0500, Steven Rostedt wrote: > On Fri, 2011-03-04 at 18:41 +0900, Hitoshi Mitake wrote: > > > BTW, how do you think about the idea of exporting data in > > python (or other neutral) expression from procfs? I feel it is a > > good idea. Communicating with unified format between user space and > > kernel space will reduce lots of parsing overhead. Is this too > > aggressive or insane? > > As I mentioned in another email, I have no problem with an easy to parse > file. But I will aggressively NAK any "python" or other scripting > language. I'm sure I would get the same response if I were to have the > kernel outputting perl language ;) Same for me. But even before talking about that, I wonder if doing this is actually needed. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/