From: David Ahern <dsahern@gmail.com>
To: Borislav Petkov <bp@alien8.de>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: adding trace-cmd's plugins to perf
Date: Tue, 12 Apr 2011 13:39:30 -0600 [thread overview]
Message-ID: <4DA4AA72.4070904@gmail.com> (raw)
In-Reply-To: <20110412190150.GC9891@liondog.tnic>
On 04/12/11 13:01, Borislav Petkov wrote:
>>> Also, just FYI, I have this RAS daemon patchset which splits perf functionality
>>> into different sub-libs, which are more or less topic based:
>>>
>>> tools/lib/trace/ - all the trace-event* stuff from Steven
>>> tools/lib/lk/ - generic enough stuff (git headers, etc) which several tools could use
Is this going to contain the option parsing as well? e.g., something
tools/kvm is picking up from perf.
>>> tools/lib/perf/ - functionality related to perf events
>>>
>>> Here's the last submission http://marc.info/?l=linux-edac&m=129562244211501&w=2
>>> and I'm currently finishing a new rebase against tip/perf/core.
>>>
>>> If you're fine with that split I'd suggest I load off my stuff first so
>>> that David can continue from there and I can finally stop rebasing like
>>> crazy each time perf moves forward.
>>>
>>> Opinions? Suggestions?
>>
>> Yeah, David, can you try Borislav's patchset and tell us what you think
>> wrt servicing your needs?
>
> Yeah, but first let me post the latest version - I'll try to do so in
> the next couple of days.
>
> Thanks.
>
Sure. This is a background task, and I still need to spend time on
trace-cmd to understand it. ie. it's not something I expect to do within
the next week -- more like within the next month if I get the time.
David
next prev parent reply other threads:[~2011-04-12 19:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-10 3:50 adding trace-cmd's plugins to perf David Ahern
2011-04-12 16:22 ` Frederic Weisbecker
2011-04-12 18:35 ` Arnaldo Carvalho de Melo
2011-04-12 18:51 ` Borislav Petkov
2011-04-12 18:56 ` Arnaldo Carvalho de Melo
2011-04-12 19:01 ` Borislav Petkov
2011-04-12 19:39 ` David Ahern [this message]
2011-04-12 20:01 ` Borislav Petkov
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=4DA4AA72.4070904@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=bp@alien8.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox