From: "Alex Bennée" <alex.bennee@linaro.org>
To: Alexander Spyridakis <a.spyridakis@virtualopensystems.com>
Cc: mttcg@listserver.greensocs.com,
"Alvise Rigo" <a.rigo@virtualopensystems.com>,
"Mark Burton" <mark.burton@greensocs.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"KONRAD Frédéric" <fred.konrad@greensocs.com>
Subject: Re: [Qemu-devel] TCG baremetal tests repo
Date: Mon, 22 Jun 2015 13:59:12 +0100 [thread overview]
Message-ID: <87lhfb99wf.fsf@linaro.org> (raw)
In-Reply-To: <CAJRNFKLMU9GNGbtRT28ziJKf-+iQnBTmW1CkvFkp+k60PajcAQ@mail.gmail.com>
Alexander Spyridakis <a.spyridakis@virtualopensystems.com> writes:
> Hello all,
>
> You can find the latest tcg atomic test payload in the following repo:
>> git clone
>https://git.virtualopensystems.com/dev/tcg_baremetal_tests.git
Both git and Chrome complain about your SSL certificates btw.
>
> You also need an arm baremetal cross-compiler like arm-none-gnueabi- (arm)
> and the usual aarch64-linux-gnu- (arm64). Due to a PSCI bug in the current
> multithreading tcg repo, the atomic test was modified to work also on the
> vexpress machine model.
>
> To run it:
>> make vexpress (or virt/virt64 for other targets)
>> ../mttcg/arm-softmmu/qemu-system-arm -nographic -M vexpress-a15 -kernel
> build-vexpress/image-vexpress.axf -smp 4
>
> On my machine it takes around 30 seconds for one run of the test and the
> results vary from as low as 5 to 30 errors per vCPU per 10 million
> iterations (no errors with KVM). It is also very interesting to note, that
> the current test finishes faster on upstream qemu than multithreaded
> qemu.
Interesting. Thanks for putting the tests online.
>
> Best regards.
--
Alex Bennée
next prev parent reply other threads:[~2015-06-22 12:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 10:54 [Qemu-devel] TCG baremetal tests repo Alexander Spyridakis
2015-06-22 12:59 ` Alex Bennée [this message]
2015-06-24 16:39 ` Alex Bennée
2015-06-24 19:09 ` Peter Maydell
2015-06-25 6:39 ` Alex Bennée
2015-06-25 16:01 ` Frederic Konrad
2015-06-26 0:26 ` Alexander Spyridakis
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=87lhfb99wf.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=a.rigo@virtualopensystems.com \
--cc=a.spyridakis@virtualopensystems.com \
--cc=fred.konrad@greensocs.com \
--cc=mark.burton@greensocs.com \
--cc=mttcg@listserver.greensocs.com \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.