linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: y.karadz@gmail.com
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH v3 0/3] trace-cruncher: Add support for event probes
Date: Thu, 27 Jan 2022 09:01:08 +0200	[thread overview]
Message-ID: <20220127070111.27529-1-tz.stoyanov@gmail.com> (raw)

Event probe (eprobe) is a new type of ftrace dynamic events, introduced
in the Linux kernel 5.15 version. It is useful to have support for them
in trace-cruncher, as it allows more flexibility when printing event's
data.

v3 changes:
 - Added eporbe example.
v2 changes:
 - Rebase.
 - Moved unit test in a separate patch.
 - Added a check in the unit test if the kernel supports eprobes.
 - Renamed the API from PyFtrace_register_eprobe() to PyFtrace_eprobe(), for
   consistency with the other dynamic events APIs.

Tzvetomir Stoyanov (VMware) (3):
  trace-cruncher: Add support for event probes
  trace-cruncher: Unit test for event probes API
  trace-cruncher: Example for event probes API

 examples/eprobe.py                            | 29 +++++++++++
 src/ftracepy-utils.c                          | 32 ++++++++++++
 src/ftracepy-utils.h                          |  2 +
 src/ftracepy.c                                |  5 ++
 .../tests/1_unit/test_01_ftracepy_unit.py     | 50 +++++++++++++++++++
 5 files changed, 118 insertions(+)
 create mode 100755 examples/eprobe.py

-- 
2.34.1


             reply	other threads:[~2022-01-27  7:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27  7:01 Tzvetomir Stoyanov (VMware) [this message]
2022-01-27  7:01 ` [PATCH v3 1/3] trace-cruncher: Add support for event probes Tzvetomir Stoyanov (VMware)
2022-01-27  7:01 ` [PATCH v3 2/3] trace-cruncher: Unit test for event probes API Tzvetomir Stoyanov (VMware)
2022-01-27  7:01 ` [PATCH v3 3/3] trace-cruncher: Example " Tzvetomir Stoyanov (VMware)
2022-01-27 10:45 ` [PATCH v3 0/3] trace-cruncher: Add support for event probes 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=20220127070111.27529-1-tz.stoyanov@gmail.com \
    --to=tz.stoyanov@gmail.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=y.karadz@gmail.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).