From: Ahmed Karaman <ahmedkhaledkaraman@gmail.com>
To: luoyonggang@gmail.com
Cc: "Lukáš Doktor" <ldoktor@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Aleksandar Markovic" <aleksandar.qemu.devel@gmail.com>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [REPORT] [GSoC - TCG Continuous Benchmarking] [#2] Dissecting QEMU Into Three Main Parts
Date: Tue, 30 Jun 2020 09:29:49 +0200 [thread overview]
Message-ID: <CALTWKrVwRhQEEjMEq444fNgBp1Dv_XyJAV7suXCEmeS40raaEQ@mail.gmail.com> (raw)
In-Reply-To: <CAE2XoE-dOHGtJO5f0xXA7r4hEeL5LDOPB1TDNPjWNC+hf9Qyew@mail.gmail.com>
On Tue, Jun 30, 2020 at 7:59 AM 罗勇刚(Yonggang Luo) <luoyonggang@gmail.com> wrote:
>
> Wonderful work, May I reproduce the work on my local machine?
>
> On Mon, Jun 29, 2020 at 6:26 PM Ahmed Karaman <ahmedkhaledkaraman@gmail.com> wrote:
>>
>> Hi,
>>
>> The second report of the TCG Continuous Benchmarking series builds
>> upon the QEMU performance metrics calculated in the previous report.
>> This report presents a method to dissect the number of instructions
>> executed by a QEMU invocation into three main phases:
>> - Code Generation
>> - JIT Execution
>> - Helpers Execution
>> It devises a Python script that automates this process.
>>
>> After that, the report presents an experiment for comparing the
>> output of running the script on 17 different targets. Many conclusions
>> can be drawn from the results and two of them are discussed in the
>> analysis section.
>>
>> Report link:
>> https://ahmedkrmn.github.io/TCG-Continuous-Benchmarking/Dissecting-QEMU-Into-Three-Main-Parts/
>>
>> Previous reports:
>> Report 1 - Measuring Basic Performance Metrics of QEMU:
>> https://lists.gnu.org/archive/html/qemu-devel/2020-06/msg06692.html
>>
>> Best regards,
>> Ahmed Karaman
>
>
>
> --
> 此致
> 礼
> 罗勇刚
> Yours
> sincerely,
> Yonggang Luo
Thanks Mr. Yonggang. Yes of course, go ahead.
Please let me know if you have any further questions.
Best Regards,
Ahmed Karaman
next prev parent reply other threads:[~2020-06-30 7:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 10:25 [REPORT] [GSoC - TCG Continuous Benchmarking] [#2] Dissecting QEMU Into Three Main Parts Ahmed Karaman
2020-06-29 10:40 ` Aleksandar Markovic
2020-06-29 14:26 ` Ahmed Karaman
2020-06-29 16:03 ` Alex Bennée
2020-06-29 18:21 ` Aleksandar Markovic
2020-06-29 21:16 ` Ahmed Karaman
2020-07-01 13:44 ` Ahmed Karaman
2020-07-01 15:42 ` Alex Bennée
2020-07-01 17:47 ` Ahmed Karaman
2020-07-03 22:46 ` Aleksandar Markovic
2020-07-04 8:45 ` Alex Bennée
2020-07-04 9:19 ` Aleksandar Markovic
2020-07-04 9:55 ` Aleksandar Markovic
2020-07-04 17:10 ` Ahmed Karaman
2020-06-30 4:33 ` Lukáš Doktor
2020-06-30 7:18 ` Ahmed Karaman
2020-06-30 8:58 ` Aleksandar Markovic
2020-06-30 12:46 ` Lukáš Doktor
2020-06-30 19:14 ` Ahmed Karaman
2020-06-30 9:41 ` Aleksandar Markovic
2020-06-30 12:58 ` Lukáš Doktor
2020-06-30 5:59 ` 罗勇刚(Yonggang Luo)
2020-06-30 7:29 ` Ahmed Karaman [this message]
2020-06-30 8:21 ` Aleksandar Markovic
2020-06-30 9:52 ` Aleksandar Markovic
2020-06-30 19:02 ` Ahmed Karaman
2020-07-01 14:47 ` 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=CALTWKrVwRhQEEjMEq444fNgBp1Dv_XyJAV7suXCEmeS40raaEQ@mail.gmail.com \
--to=ahmedkhaledkaraman@gmail.com \
--cc=aleksandar.qemu.devel@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=ldoktor@redhat.com \
--cc=luoyonggang@gmail.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).