From: Zamir SUN <sztsian@gmail.com>
To: linux-trace-devel@vger.kernel.org
Cc: tstoyanov@vmware.com, Jiri Olsa <jolsa@redhat.com>, zsun@redhat.com
Subject: Re: Co-existing of traceevent of trace-cmd and perf
Date: Tue, 29 Sep 2020 22:16:33 +0800 [thread overview]
Message-ID: <3dc91d46-e359-472b-4faf-d9b324cc4c8d@gmail.com> (raw)
In-Reply-To: <1baba359-fd07-1a61-0158-e65c6b06425f@gmail.com>
On 9/29/20 9:44 PM, Zamir SUN wrote:
> Hi,
>
> I'm packaging trace-cmd 2.9 into Fedora.
>
> Back in trace-cmd 2.8, all the plugins are under
> $(libdir)/trace-cmd/plugins. While as of trace-cmd 2.9, I find the
> traceevent plugins are installed in $(libdir) by default. This brings up
> an interesting situation - the perf tool also contains a copy of the
> traceevent in the same directory. So this means trace-cmd and perf have
> file conflicts. In terms of packaging, this means users can only install
> one of them, not in parallel (at least for Fedora). So I'd like to see
> if there are existing proposals or suggestions for which one is expected
> to be used by other utilities? Or is there any official plan to move one
> of them to the other directory?
>
> I'm copying Tzvetomir and Jiri as I think you're the first people for
> getting the plugins in this directory for trace-cmd and perf respectively.
>
Sorry, I just saw an email from Steven mentioning there will be a stand
alone libtraceevent. However I did not find it in git.kernel.org. So I
probably should ask if the stand alone version of libtraceevent is ready
now?
Thanks.
> Thanks in advance.
>
--
Zamir SUN
Fedora user
GPG : 1D86 6D4A 49CE 4BBD 72CF FCF5 D856 6E11 F2A0 525E
next prev parent reply other threads:[~2020-09-29 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 13:44 Co-existing of traceevent of trace-cmd and perf Zamir SUN
2020-09-29 14:16 ` Zamir SUN [this message]
2020-09-29 15:18 ` Steven Rostedt
2020-10-04 7:07 ` Zamir SUN
2020-09-30 17:21 ` Vitaly Chikunov
2020-10-04 7:09 ` Zamir SUN
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=3dc91d46-e359-472b-4faf-d9b324cc4c8d@gmail.com \
--to=sztsian@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=tstoyanov@vmware.com \
--cc=zsun@redhat.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).