From: Josef Bacik <jbacik@fb.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] trace-cmd: add the ability to install libtracecmd
Date: Fri, 11 Jul 2014 14:27:17 -0400 [thread overview]
Message-ID: <53C02C85.7000304@fb.com> (raw)
In-Reply-To: <20140710185311.5672b6e6@gandalf.local.home>
On 07/10/2014 06:53 PM, Steven Rostedt wrote:
> On Thu, 10 Jul 2014 17:22:45 -0400
> Josef Bacik <jbacik@fb.com> wrote:
>
>> Hello,
>>
>> I'm trying to build some custom tracing tools on top of trace-cmd but they
>> aren't really usefull outside of Facebook so I don't want to shove them into the
>> actual trace-cmd project. Instead I'd like to be able to just build libtracecmd
>> and install that as well as the necessary header files and just link my tools
>> against that. I'm shit at userspace stuff like this, so I've just hacked
>> something together that works for me. I'm mostly hoping somebody will look at
>> the Makefile horribleness that I came up with and tell me how to do it right (or
>> better yet do it for me!) The second patch just cleans up some stuff to make
>> the shared library more library esque. Any feedback would be great. Thanks,
>>
>
> I'm shit at userspace too ;-) I just like simple makefiles and other
> non "autocrap" stuff.
>
> Anyway, I did plan on getting a libtracecmd out someday (at a bottom of
> a very long todo list), so I'm all game for this. I was hoping to get
> libtraceevent out first. That's now homed in the kernel tools
> directory and I've been porting stuff to and from trace-cmd for that as
> well. But there's still a bit of work on that front.
>
> I'll have to take a look at your patches and see how they are after I
> get some other things out of the way first.
>
Ok I didn't notice the libtracecmd, so I'll send the second patch
against that since it's just against the event parse stuff. In reality
all I need is the event parsing stuff, I just use the libtracecmd to
open the trace.dat file. I'll see if I can figure out how to just parse
the events live without having to record with trace-cmd first and that
will probably be good enough for me for now, then maybe when I care
about post-processing trace.dat you will have gotten to the bottom of
your TODO list. Thanks,
Josef
prev parent reply other threads:[~2014-07-11 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 21:22 [RFC] trace-cmd: add the ability to install libtracecmd Josef Bacik
2014-07-10 21:22 ` [PATCH 1/2] trace-cmd: add install_libs target to trace-cmd Josef Bacik
2014-07-10 21:22 ` [PATCH 2/2] trace-cmd: make libtracecmd a little more library friendly Josef Bacik
2014-07-10 22:53 ` [RFC] trace-cmd: add the ability to install libtracecmd Steven Rostedt
2014-07-11 18:27 ` Josef Bacik [this message]
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=53C02C85.7000304@fb.com \
--to=jbacik@fb.com \
--cc=linux-kernel@vger.kernel.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.