From: Steven Rostedt <rostedt@goodmis.org>
To: Patrick McLean <chutzpah@gentoo.org>
Cc: Yordan Karadzhov <ykaradzhov@vmware.com>,
linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] kernel-shark: Reorder the priority when searching for trace-cmd libs
Date: Wed, 13 Mar 2019 15:06:02 -0400 [thread overview]
Message-ID: <20190313150602.0bed3d1f@gandalf.local.home> (raw)
In-Reply-To: <20190313114235.7fc6ce3b@patrickm>
On Wed, 13 Mar 2019 11:42:35 -0700
Patrick McLean <chutzpah@gentoo.org> wrote:
> (especially when trace-cmd and trace-cmd are
> separate packages)
That should be a fun stunt. ;-)
But yeah, we are looking into separating KernelShark out of trace-cmd
in the future, but depending on libftrace.so (the guts of trace-cmd)
when that is ready. First we need to finish libtraceevent.so, which
will live in the Linux kernel git repo under tools/lib/traceeevent.
Would that be an issue in packaging libtraceevent?
-- Steve
next prev parent reply other threads:[~2019-03-13 19:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 15:22 [PATCH v2 0/3] Tuning the KernelShark build system Yordan Karadzhov
2019-03-13 15:22 ` [PATCH v2 1/3] kernel-shark: Reorder the priority when searching for trace-cmd libs Yordan Karadzhov
2019-03-13 18:42 ` Patrick McLean
2019-03-13 19:06 ` Steven Rostedt [this message]
2019-03-13 20:32 ` Patrick McLean
2019-03-18 18:47 ` Steven Rostedt
2019-03-18 20:53 ` Patrick McLean
2019-03-26 12:58 ` Steven Rostedt
2019-03-26 13:35 ` Yordan Karadzhov (VMware)
2019-03-26 13:57 ` Steven Rostedt
2019-03-27 0:24 ` Patrick McLean
2019-03-26 15:08 ` Steven Rostedt
2019-03-13 15:22 ` [PATCH v2 2/3] kernel-shark: Configuration information in ${HOME}/.cache/kernelshark Yordan Karadzhov
2019-03-26 20:51 ` Steven Rostedt
2019-03-27 8:58 ` Yordan Karadzhov
2019-03-27 13:07 ` Steven Rostedt
2019-03-13 15:22 ` [PATCH v2 3/3] kernel-shark: Set the configuration cache directory via env. variable Yordan Karadzhov
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=20190313150602.0bed3d1f@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=chutzpah@gentoo.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=ykaradzhov@vmware.com \
/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;
as well as URLs for NNTP newsgroup(s).