From: Stefan Weil <sw@weilnetz.de>
To: Thomas Huth <thuth@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] tcg/tci: do not use ldst label (never implemented)
Date: Tue, 12 Sep 2017 11:20:12 +0200 [thread overview]
Message-ID: <15608989-cb43-a522-9a7d-b57b3a393155@weilnetz.de> (raw)
In-Reply-To: <cff16e31-4be0-9665-62d7-88a12b6d0b56@weilnetz.de>
Am 12.09.2017 um 10:52 schrieb Stefan Weil:
> Am 11.09.2017 um 20:24 schrieb Peter Maydell:
>> I've also turned on a tci compile check on my pre-merge tests.
>> (It doesn't pass "make check" for me, though...) thanks -- PMM
>
> "make check-qtest-ppc64" fails for me, too.
>
> Thomas, this seems to be again the well known timing problem
> in tests/prom-env-test.c. The time for the test had been
> changedfrom 30 s to 10 s to 120 s in the past.
... changed from 10 s to 30 s to 120 s ...
> For TCI, even that latest value is not sufficient when
> testing with pseries. Of course that also depends on other
> parameters (speed of test machine, compiler flags).
>
> In my test pseries took nearly 5 minutes, so the test passes
> when the loop upper limit is increased to 30000.
Timing data for prom-env-test with TCI on another test machine:
mac99: 78 s
g3beige: 74 s
pseries: 477 s
>
> Is there a better way to handle this test? Why does pseries
> still need much more time than the other machines
> (not only with TCI)?
>
> Regards,
> Stefan
next prev parent reply other threads:[~2017-09-12 9:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 2:28 [Qemu-devel] [PATCH] tcg/tci: do not use ldst label (never implemented) Philippe Mathieu-Daudé
2017-09-11 5:18 ` Stefan Weil
2017-09-11 18:01 ` Richard Henderson
2017-09-11 18:24 ` Peter Maydell
2017-09-11 19:39 ` Stefan Weil
2017-09-11 19:47 ` Philippe Mathieu-Daudé
2017-09-11 19:54 ` Stefan Weil
2017-09-11 20:26 ` Stefan Weil
2017-09-11 21:06 ` Philippe Mathieu-Daudé
2017-09-12 8:52 ` Stefan Weil
2017-09-12 9:20 ` Stefan Weil [this message]
2017-09-12 14:56 ` Thomas Huth
2017-09-12 15:13 ` Paolo Bonzini
2017-09-21 9:59 ` Thomas Huth
2017-09-22 13:31 ` Richard Henderson
2017-09-11 18:13 ` Philippe Mathieu-Daudé
2017-09-11 18:14 ` Peter Maydell
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=15608989-cb43-a522-9a7d-b57b3a393155@weilnetz.de \
--to=sw@weilnetz.de \
--cc=f4bug@amsat.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.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 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.