From: Ahmed Karaman <ahmedkhaledkaraman@gmail.com>
To: qemu-devel@nongnu.org, aleksandar.qemu.devel@gmail.com,
philmd@redhat.com, alex.bennee@linaro.org, eblake@redhat.com,
ldoktor@redhat.com, rth@twiddle.net, ehabkost@redhat.com,
crosa@redhat.com
Cc: Ahmed Karaman <ahmedkhaledkaraman@gmail.com>
Subject: [PATCH v2 0/2] Add list_fn_callees.py and list_helpers.py scripts
Date: Thu, 16 Jul 2020 12:39:19 +0200 [thread overview]
Message-ID: <20200716103921.6605-1-ahmedkhaledkaraman@gmail.com> (raw)
Hi,
This series adds the two new scripts introduced in report 4 of the
"TCG Continuous Benchmarking" GSoC project.
"list_fn_callees.py" is used for printing the callees of a given list
of QEMU functions.
"list_helpers.py" is used for printing the executed helpers of a QEMU
invocation.
To learn more about how the scripts work and how they can be used for
analyzing the performance of different targets, please check the
"Listing QEMU Helpers and Function Callees" report.
Report link:
https://lists.nongnu.org/archive/html/qemu-devel/2020-07/msg04227.html
Best regards,
Ahmed Karaman
v1->v2:
- Indent script example output in commit message to pass the "Test checkpatch"
on patchew.
Ahmed Karaman (2):
scripts/performance: Add list_fn_callees.py script
scripts/performance: Add list_helpers.py script
scripts/performance/list_fn_callees.py | 228 +++++++++++++++++++++++++
scripts/performance/list_helpers.py | 207 ++++++++++++++++++++++
2 files changed, 435 insertions(+)
create mode 100755 scripts/performance/list_fn_callees.py
create mode 100755 scripts/performance/list_helpers.py
--
2.17.1
next reply other threads:[~2020-07-16 10:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 10:39 Ahmed Karaman [this message]
2020-07-16 10:39 ` [PATCH v2 1/2] scripts/performance: Add list_fn_callees.py script Ahmed Karaman
2020-07-16 10:39 ` [PATCH v2 2/2] scripts/performance: Add list_helpers.py script Ahmed Karaman
2020-07-28 10:30 ` Aleksandar Markovic
2020-07-28 10:43 ` Aleksandar Markovic
2020-07-28 10:51 ` Aleksandar Markovic
2020-07-28 16:55 ` Ahmed Karaman
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=20200716103921.6605-1-ahmedkhaledkaraman@gmail.com \
--to=ahmedkhaledkaraman@gmail.com \
--cc=aleksandar.qemu.devel@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--cc=eblake@redhat.com \
--cc=ehabkost@redhat.com \
--cc=ldoktor@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).