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 0/1] Add bisect.py script
Date: Wed, 22 Jul 2020 01:15:35 +0200 [thread overview]
Message-ID: <20200721231536.21604-1-ahmedkhaledkaraman@gmail.com> (raw)
Hi,
This series adds the new bisect.py script introduced in report 5 of
the "TCG Continuous Benchmarking" GSoC project.
The script is used for locating the commit that caused a performance
degradation or improvement in QEMU using the git bisect command
(binary search).
To learn more about how the script works and how it can be used for
detecting two commits, one that introduced a performance degradation
in PowerPC targets, and the other introducing a performance
improvement in MIPS, please check the
"Finding Commits Affecting QEMU Performance" report.
Report link:
https://lists.nongnu.org/archive/html/qemu-devel/2020-07/msg05769.html
Best regards,
Ahmed Karaman
Ahmed Karaman (1):
scripts/performance: Add bisect.py script
scripts/performance/bisect.py | 374 ++++++++++++++++++++++++++++++++++
1 file changed, 374 insertions(+)
create mode 100755 scripts/performance/bisect.py
--
2.17.1
next reply other threads:[~2020-07-21 23:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 23:15 Ahmed Karaman [this message]
2020-07-21 23:15 ` [PATCH 1/1] scripts/performance: Add bisect.py script Ahmed Karaman
2020-07-25 2:11 ` John Snow
2020-07-25 12:31 ` Aleksandar Markovic
2020-07-25 12:58 ` Ahmed Karaman
2020-07-25 19:48 ` Aleksandar Markovic
2020-07-25 20:48 ` Ahmed Karaman
2020-07-27 19:11 ` John Snow
2020-07-27 22:05 ` Aleksandar Markovic
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=20200721231536.21604-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).