From: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
To: linux-trace-devel@vger.kernel.org
Cc: rostedt@goodmis.org, Valentin.Schneider@arm.com,
douglas.raillard@arm.com,
"Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
Subject: [PATCH 0/5] Build trace-cruncher as Python pakage
Date: Thu, 12 Dec 2019 11:02:27 +0200 [thread overview]
Message-ID: <20191212090232.24236-1-y.karadz@gmail.com> (raw)
This patch-set is an attempt to restructure the project and to make it
build as a native Python package. Although it looks like a complete
rewrite, this is essentially just a switching from using Cython to using
directly the C API of Python. Cython is still being used but only for
the implementation of the NumPy data wrapper. The new package has its
own stand-alone build system (very primitive for the moment) that is
completely decoupled from the existing build system used by tracecruncher.
In order to build and install the new package do:
sudo python setup.py install --record files.txt
The patch-set does not remove the old implementation yet. This will
happen in another successive patch-set.
Please review as careful as possible!
Yordan Karadzhov (VMware) (5):
Refactor the part of the interface that relies on libkshark
Refactor the part of the interface that relies on libtraceevent
Refactor NumPy based data wrapper
Add "utils"
Adapt the sched_wakeup.py example script to use the new tracecruncher
module
examples/sched_wakeup.py | 30 ++---
setup.py | 61 +++++++++
src/common.h | 20 +++
src/datawrapper.pyx | 201 ++++++++++++++++++++++++++++
src/ftracepy.c | 234 +++++++++++++++++++++++++++++++++
src/ksharkpy.c | 268 ++++++++++++++++++++++++++++++++++++++
src/trace2matrix.c | 29 +++++
tracecruncher/__init__.py | 0
tracecruncher/utils.py | 54 ++++++++
9 files changed, 882 insertions(+), 15 deletions(-)
create mode 100644 setup.py
create mode 100644 src/common.h
create mode 100644 src/datawrapper.pyx
create mode 100644 src/ftracepy.c
create mode 100644 src/ksharkpy.c
create mode 100644 src/trace2matrix.c
create mode 100644 tracecruncher/__init__.py
create mode 100644 tracecruncher/utils.py
--
2.20.1
next reply other threads:[~2019-12-12 9:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 9:02 Yordan Karadzhov (VMware) [this message]
2019-12-12 9:02 ` [PATCH 1/5] Refactor the part of the interface that relies on libkshark Yordan Karadzhov (VMware)
2019-12-12 9:02 ` [PATCH 2/5] Refactor the part of the interface that relies on libtraceevent Yordan Karadzhov (VMware)
2019-12-12 9:02 ` [PATCH 3/5] Refactor NumPy based data wrapper Yordan Karadzhov (VMware)
2019-12-12 9:02 ` [PATCH 4/5] Add "utils" Yordan Karadzhov (VMware)
2019-12-12 9:02 ` [PATCH 5/5] Adapt the sched_wakeup.py example script to use the new tracecruncher module Yordan Karadzhov (VMware)
2019-12-31 18:37 ` [PATCH 0/5] Build trace-cruncher as Python pakage Douglas Raillard
2020-01-07 16:59 ` 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=20191212090232.24236-1-y.karadz@gmail.com \
--to=y.karadz@gmail.com \
--cc=Valentin.Schneider@arm.com \
--cc=douglas.raillard@arm.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.