From: "Emilio G. Cota" <cota@braap.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: mttcg@listserver.greensocs.com, qemu-devel@nongnu.org,
fred.konrad@greensocs.com, a.rigo@virtualopensystems.com,
serge.fdrv@gmail.com, bobby.prani@gmail.com, rth@twiddle.net,
mark.burton@greensocs.com, pbonzini@redhat.com,
jan.kiszka@siemens.com, peter.maydell@linaro.org,
claudio.fontana@huawei.com
Subject: Re: [Qemu-devel] [PATCH 0/2] Reduce lock contention on TCG hot-path
Date: Fri, 1 Jul 2016 20:52:29 -0400 [thread overview]
Message-ID: <20160702005229.GC2295@flamenco> (raw)
In-Reply-To: <1467389770-9738-1-git-send-email-alex.bennee@linaro.org>
On Fri, Jul 01, 2016 at 17:16:08 +0100, Alex Bennée wrote:
(snip)
> run 1: ret=0 (PASS), time=4.755824 (1/1)
> run 2: ret=0 (PASS), time=4.756076 (2/2)
> run 3: ret=0 (PASS), time=4.755916 (3/3)
> run 4: ret=0 (PASS), time=4.755853 (4/4)
> run 5: ret=0 (PASS), time=4.755929 (5/5)
> Results summary:
> 0: 5 times (100.00%), avg time 4.755920 (0.000000 deviation)
(snip)
> run 1: ret=0 (PASS), time=9.761559 (1/1)
> run 2: ret=0 (PASS), time=9.511616 (2/2)
> run 3: ret=0 (PASS), time=9.761713 (3/3)
> run 4: ret=0 (PASS), time=10.262504 (4/4)
> run 5: ret=0 (PASS), time=9.762059 (5/5)
> Results summary:
> 0: 5 times (100.00%), avg time 9.811890 (0.060150 deviation)
This is a needless diversion, but I was explaining this stuff today
to a student so couldn't help but notice.
The computed deviations seem overly small. For instance, the corrected sample
standard deviation ( https://en.wikipedia.org/wiki/Standard_deviation )
(which is usually referred to as "standard deviation", or "error")
for the last test should be 0.2742 instead of 0.06.
How are they being computed? I tried to find the source of your script
(in the kvm-unit-tests repo) but couldn't find it.
Thanks,
Emilio
next prev parent reply other threads:[~2016-07-02 0:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 16:16 [Qemu-devel] [PATCH 0/2] Reduce lock contention on TCG hot-path Alex Bennée
2016-07-01 16:16 ` [Qemu-devel] [PATCH 1/2] tcg: Ensure safe tb_jmp_cache lookup out of 'tb_lock' Alex Bennée
2016-07-01 23:14 ` Richard Henderson
2016-07-02 0:17 ` Emilio G. Cota
2016-07-02 0:32 ` Richard Henderson
2016-07-04 22:33 ` Emilio G. Cota
2016-07-02 7:09 ` Alex Bennée
2016-07-04 22:31 ` Emilio G. Cota
2016-07-05 12:49 ` Paolo Bonzini
2016-07-01 16:16 ` [Qemu-devel] [PATCH 2/2] cpu-exec: remove tb_lock from the hot-path Alex Bennée
2016-07-01 23:19 ` Richard Henderson
2016-07-02 0:39 ` Emilio G. Cota
2016-07-04 11:45 ` Alex Bennée
2016-07-04 22:30 ` Emilio G. Cota
2016-07-05 11:14 ` Alex Bennée
2016-07-05 12:47 ` Paolo Bonzini
2016-07-05 13:11 ` Alex Bennée
2016-07-05 13:42 ` Paolo Bonzini
2016-07-05 15:34 ` Sergey Fedorov
2016-07-05 16:00 ` Alex Bennée
2016-07-05 16:04 ` Sergey Fedorov
2016-07-02 0:52 ` Emilio G. Cota [this message]
2016-07-02 7:08 ` [Qemu-devel] [PATCH 0/2] Reduce lock contention on TCG hot-path Alex Bennée
2016-07-02 16:03 ` Paolo Bonzini
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=20160702005229.GC2295@flamenco \
--to=cota@braap.org \
--cc=a.rigo@virtualopensystems.com \
--cc=alex.bennee@linaro.org \
--cc=bobby.prani@gmail.com \
--cc=claudio.fontana@huawei.com \
--cc=fred.konrad@greensocs.com \
--cc=jan.kiszka@siemens.com \
--cc=mark.burton@greensocs.com \
--cc=mttcg@listserver.greensocs.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=serge.fdrv@gmail.com \
/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).