From: Frederic Weisbecker <fweisbec@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux-kernel@vger.kernel.org, h.mitake@gmail.com,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: [PATCH] perf lock: clean the options for perf record
Date: Fri, 4 Mar 2011 15:41:22 +0100 [thread overview]
Message-ID: <20110304144119.GE1972@nowhere> (raw)
In-Reply-To: <1299249438.20306.3.camel@gandalf.stny.rr.com>
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.
next prev parent reply other threads:[~2011-03-04 14:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 15:28 [PATCH] perf lock: clean the options for perf record Hitoshi Mitake
2011-02-22 15:30 ` Hitoshi Mitake
2011-02-22 15:43 ` Peter Zijlstra
2011-02-22 18:22 ` Frederic Weisbecker
2011-02-23 4:17 ` Hitoshi Mitake
2011-02-24 15:46 ` Hitoshi Mitake
2011-02-24 16:50 ` Frederic Weisbecker
2011-02-25 17:10 ` Hitoshi Mitake
2011-02-28 15:00 ` [PATCH] lockstat: export data in python expression Hitoshi Mitake
2011-02-28 18:07 ` Peter Zijlstra
2011-02-28 23:48 ` Hitoshi Mitake
2011-03-04 14:08 ` Steven Rostedt
2011-03-01 14:55 ` [PATCH] perf lock: clean the options for perf record Frederic Weisbecker
2011-03-04 9:41 ` Hitoshi Mitake
2011-03-04 13:56 ` Frederic Weisbecker
2011-03-04 13:58 ` Peter Zijlstra
2011-03-04 14:21 ` Frederic Weisbecker
2011-03-09 16:41 ` Hitoshi Mitake
2011-03-04 14:37 ` Steven Rostedt
2011-03-04 14:41 ` Frederic Weisbecker [this message]
2011-03-05 17:20 ` Hitoshi Mitake
2011-03-05 17:14 ` Hitoshi Mitake
2011-02-22 18:09 ` Frederic Weisbecker
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=20110304144119.GE1972@nowhere \
--to=fweisbec@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=h.mitake@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mitake@dcl.info.waseda.ac.jp \
--cc=paulus@samba.org \
--cc=rostedt@goodmis.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.