From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: linux-trace-devel@vger.kernel.org
Subject: [PATCH v4 1/3] trace-cruncher: ftrace uprobe raw API
Date: Tue, 28 Jun 2022 15:16:19 +0300 [thread overview]
Message-ID: <20220628121621.572506-2-tz.stoyanov@gmail.com> (raw)
In-Reply-To: <20220628121621.572506-1-tz.stoyanov@gmail.com>
Trace-cruncher low level wrappers for tracefs library APIs for
uprobe and uretprobe allocation.
Signed-off-by: Tzvetomir Stoyanov (VMware) <tz.stoyanov@gmail.com>
---
src/ftracepy-utils.c | 48 ++++++++++++++++++++++++++++++++++++++++++++
src/ftracepy-utils.h | 4 ++++
src/ftracepy.c | 10 +++++++++
3 files changed, 62 insertions(+)
diff --git a/src/ftracepy-utils.c b/src/ftracepy-utils.c
index e8411ae..b39459b 100644
--- a/src/ftracepy-utils.c
+++ b/src/ftracepy-utils.c
@@ -2449,6 +2449,54 @@ PyObject *PyFtrace_eprobe(PyObject *self, PyObject *args, PyObject *kwargs)
return py_dyn;
}
+static PyObject *alloc_uprobe(PyObject *self, PyObject *args, PyObject *kwargs, bool pret)
+{
+ static char *kwlist[] = {"event", "file", "offset", "fetch_args", NULL};
+ const char *event, *file, *fetchargs = NULL;
+ unsigned long long offset;
+ struct tracefs_dynevent *uprobe;
+ PyObject *py_dyn;
+
+ if (!PyArg_ParseTupleAndKeywords(args,
+ kwargs,
+ "ssK|s",
+ kwlist,
+ &event,
+ &file,
+ &offset,
+ &fetchargs)) {
+ return NULL;
+ }
+
+ if (pret)
+ uprobe = tracefs_uretprobe_alloc(TC_SYS, event, file, offset, fetchargs);
+ else
+ uprobe = tracefs_uprobe_alloc(TC_SYS, event, file, offset, fetchargs);
+ if (!uprobe) {
+ MEM_ERROR;
+ return NULL;
+ }
+
+ py_dyn = PyDynevent_New(uprobe);
+ /*
+ * Here we only allocated and initializes a dynamic event object.
+ * However, no dynamic event is added to the system yet. Hence,
+ * there is no need to 'destroy' this event at exit.
+ */
+ set_destroy_flag(py_dyn, false);
+ return py_dyn;
+}
+
+PyObject *PyFtrace_uprobe(PyObject *self, PyObject *args, PyObject *kwargs)
+{
+ return alloc_uprobe(self, args, kwargs, false);
+}
+
+PyObject *PyFtrace_uretprobe(PyObject *self, PyObject *args, PyObject *kwargs)
+{
+ return alloc_uprobe(self, args, kwargs, true);
+}
+
static PyObject *set_filter(PyObject *args, PyObject *kwargs,
struct tep_handle *tep,
struct tep_event *event)
diff --git a/src/ftracepy-utils.h b/src/ftracepy-utils.h
index 9491b18..e6fab69 100644
--- a/src/ftracepy-utils.h
+++ b/src/ftracepy-utils.h
@@ -257,6 +257,10 @@ PyObject *PyFtrace_kretprobe(PyObject *self, PyObject *args, PyObject *kwargs);
PyObject *PyFtrace_eprobe(PyObject *self, PyObject *args, PyObject *kwargs);
+PyObject *PyFtrace_uprobe(PyObject *self, PyObject *args, PyObject *kwargs);
+
+PyObject *PyFtrace_uretprobe(PyObject *self, PyObject *args, PyObject *kwargs);
+
PyObject *PyFtrace_hist(PyObject *self, PyObject *args,
PyObject *kwargs);
diff --git a/src/ftracepy.c b/src/ftracepy.c
index 2819da2..29d273f 100644
--- a/src/ftracepy.c
+++ b/src/ftracepy.c
@@ -483,6 +483,16 @@ static PyMethodDef ftracepy_methods[] = {
METH_VARARGS | METH_KEYWORDS,
PyFtrace_eprobe_doc,
},
+ {"uprobe",
+ (PyCFunction) PyFtrace_uprobe,
+ METH_VARARGS | METH_KEYWORDS,
+ "Define a uprobe."
+ },
+ {"uretprobe",
+ (PyCFunction) PyFtrace_uretprobe,
+ METH_VARARGS | METH_KEYWORDS,
+ "Define a uretprobe."
+ },
{"hist",
(PyCFunction) PyFtrace_hist,
METH_VARARGS | METH_KEYWORDS,
--
2.35.3
next prev parent reply other threads:[~2022-06-28 12:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 12:16 [PATCH v4 0/3] trace-cruncher: ftrace uprobes support Tzvetomir Stoyanov (VMware)
2022-06-28 12:16 ` Tzvetomir Stoyanov (VMware) [this message]
2022-06-28 12:16 ` [PATCH v4 2/3] trace-cruncher: High level wrappers for ftrace uprobes Tzvetomir Stoyanov (VMware)
2022-06-28 12:16 ` [PATCH v4 3/3] trace-cruncher: Example script for uprobes high level API Tzvetomir Stoyanov (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=20220628121621.572506-2-tz.stoyanov@gmail.com \
--to=tz.stoyanov@gmail.com \
--cc=linux-trace-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).