All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH 2/2] KernelShark2.0: Use libtracefs APIs to access tracefs
Date: Fri,  6 Mar 2020 11:29:02 +0200	[thread overview]
Message-ID: <20200306092902.48786-3-tz.stoyanov@gmail.com> (raw)
In-Reply-To: <20200306092902.48786-1-tz.stoyanov@gmail.com>

From: Tzvetomir (VMware)  Stoyanov <tz.stoyanov@gmail.com>

KernelShark uses trace-cmd APIs to access tracefs. Now those
APIs are moved to libtracefs:
 tracecmd_get_tracing_dir() -> tracefs_get_tracing_dir()
 tracecmd_local_events() -> tracefs_local_events()
 tracecmd_local_plugins() -> tracefs_tracers()

Signed-off-by: Tzvetomir (VMware)  Stoyanov <tz.stoyanov@gmail.com>
---
 src/libkshark-tepdata.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/src/libkshark-tepdata.c b/src/libkshark-tepdata.c
index ed61f76..8678e12 100644
--- a/src/libkshark-tepdata.c
+++ b/src/libkshark-tepdata.c
@@ -19,6 +19,7 @@
 
 // trace-cmd
 #include "trace-cmd/trace-cmd.h"
+#include "tracefs/tracefs.h"
 
 // KernelShark
 #include "libkshark-plugin.h"
@@ -1066,7 +1067,7 @@ int kshark_tep_init_local(struct kshark_data_stream *stream)
 	if (!tep_handle)
 		return -EFAULT;
 
-	tep_handle->tep = tracecmd_local_events(tracecmd_get_tracing_dir());
+	tep_handle->tep = tracefs_local_events(tracefs_get_tracing_dir());
 	if (!tep_handle->tep)
 		goto fail;
 
@@ -1233,5 +1234,5 @@ int kshark_tep_get_event_fields(struct kshark_data_stream *stream,
 /** Get an array of available tracer plugins. */
 char **kshark_tracecmd_local_plugins()
 {
-	return tracecmd_local_plugins(tracecmd_get_tracing_dir());
+	return tracefs_tracers(tracefs_get_tracing_dir());
 }
-- 
2.24.1


  parent reply	other threads:[~2020-03-06  9:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-06  9:29 [PATCH 0/2] KernelShark2.0: Use libtracefs APIs to access tracefs Tzvetomir Stoyanov (VMware)
2020-03-06  9:29 ` [PATCH 1/2] KernelShark2.0: Link KernelShark to libtracefs Tzvetomir Stoyanov (VMware)
2020-03-06  9:29 ` Tzvetomir Stoyanov (VMware) [this message]
2020-03-06 20:13 ` [PATCH 0/2] KernelShark2.0: Use libtracefs APIs to access tracefs Steven Rostedt
2020-03-06 22:34   ` Steven Rostedt
2020-03-09  9:17     ` Yordan Karadzhov (VMware)
2020-03-09 15:44       ` Steven Rostedt
2020-03-09 16:30         ` Steven Rostedt
2020-03-09  9:10   ` Yordan Karadzhov (VMware)

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=20200306092902.48786-3-tz.stoyanov@gmail.com \
    --to=tz.stoyanov@gmail.com \
    --cc=linux-trace-devel@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.