From: Ahmed Karaman <ahmedkhaledkaraman@gmail.com>
To: "QEMU Developers" <qemu-devel@nongnu.org>,
"Aleksandar Markovic" <aleksandar.qemu.devel@gmail.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Eric Blake" <eblake@redhat.com>,
"Lukáš Doktor" <ldoktor@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Richard Henderson" <rth@twiddle.net>,
luoyonggang@gmail.com, "John Snow" <jsnow@redhat.com>
Subject: [REPORT] [GSoC - TCG Continuous Benchmarking] [#10] Measuring QEMU Performance in System Mode - Part Two
Date: Fri, 28 Aug 2020 12:30:00 +0200 [thread overview]
Message-ID: <CALTWKrUL_x7VQCsUVxLnMwH9=snQGd57sreWjRAe7RsBa8oS0w@mail.gmail.com> (raw)
Greetings,
In part two of the final TCG Continuous Benchmarking report, the same
procedures introduced in part one are used for inspecting the
performance of QEMU system mode emulation. The only difference is
instead of emulating the same OS for all targets, different images
where selected from the Qemu-devel thread below and the official QEMU
documentation.
https://www.mail-archive.com/qemu-devel@nongnu.org/msg604682.html
For each of the five targets used in this report (arm, hppa, m68k,
mipsel, and sh4), the source of the used emulation instructions is
mentioned. This is followed by a snippet for fetching the required
files and starting the system emulation.
The results of running the time command are then displayed for
measuring the boot-up time until the login screen is reached where the
emulation is stopped. The top 25 executed QEMU functions are also
measured using the topN_system.py script introduced in part one of the
report.
Report link:
https://ahmedkrmn.github.io/TCG-Continuous-Benchmarking/Measuring-QEMU-Performance-in-System-Mode-Part-Two/
Previous reports:
Report 1 - Measuring Basic Performance Metrics of QEMU:
https://lists.gnu.org/archive/html/qemu-devel/2020-06/msg06692.html
Report 2 - Dissecting QEMU Into Three Main Parts:
https://lists.gnu.org/archive/html/qemu-devel/2020-06/msg09441.html
Report 3 - QEMU 5.0 and 5.1-pre-soft-freeze Dissect Comparison:
https://lists.gnu.org/archive/html/qemu-devel/2020-07/msg01978.html
Report 4 - Listing QEMU Helpers and Function Callees:
https://lists.gnu.org/archive/html/qemu-devel/2020-07/msg04227.html
Report 5 - Finding Commits Affecting QEMU Performance:
https://lists.gnu.org/archive/html/qemu-devel/2020-07/msg05769.html
Report 6 - Performance Comparison of Two QEMU Builds:
https://lists.gnu.org/archive/html/qemu-devel/2020-07/msg07389.html
Report 7 - Measuring QEMU Emulation Efficiency:
https://lists.gnu.org/archive/html/qemu-devel/2020-08/msg00098.html
Report 8 - QEMU Nightly Performance Tests:
https://lists.gnu.org/archive/html/qemu-devel/2020-08/msg03409.html
Report 9 - Measuring QEMU Performance in System Mode:
https://lists.gnu.org/archive/html/qemu-devel/2020-08/msg05705.html
Best regards,
Ahmed Karaman
reply other threads:[~2020-08-28 10:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CALTWKrUL_x7VQCsUVxLnMwH9=snQGd57sreWjRAe7RsBa8oS0w@mail.gmail.com' \
--to=ahmedkhaledkaraman@gmail.com \
--cc=aleksandar.qemu.devel@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=eblake@redhat.com \
--cc=jsnow@redhat.com \
--cc=ldoktor@redhat.com \
--cc=luoyonggang@gmail.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).