diff options
author | Thomas Huth <thuth@redhat.com> | 2018-02-12 12:13:38 +0100 |
---|---|---|
committer | Thomas Huth <thuth@redhat.com> | 2018-02-14 11:43:42 +0100 |
commit | 9c29830c90d82f27f2152da187b29c71995e63b1 (patch) | |
tree | 4b6d3a8ecb7343aa316c641b454c49d88f4ed222 /tests/i440fx-test.c | |
parent | ec2e988fce1b262b802ef7285981629a8417cd8c (diff) | |
download | qemu-9c29830c90d82f27f2152da187b29c71995e63b1.zip qemu-9c29830c90d82f27f2152da187b29c71995e63b1.tar.gz qemu-9c29830c90d82f27f2152da187b29c71995e63b1.tar.bz2 |
tests/m48t59: Fix and re-enable the test for sparc
The m48t59 test has been disabled in commit baeddded5fe6fa37d13fb94bf8d
("sparc: disable qtest in make check"), likely due to some timing issues
in the bcd_check_time tests which might fail if it gets interrupted for
too long. It should be OK to re-enable this test if we make sure that we
do not run it on timing-sensitive machines, thus it should be OK if we only
run it in the g_test_slow() mode.
Additionally, there are two other issues:
First, the test can not run so easily on sparc64 anymore, since commit
f3b18f35a23c60edbda6420cd ("sun4u: switch m48t59 NVRAM to MMIO access")
moved the m48t59 device to the ebus instead, and for this you first
have to set up the corresponding PCI device (which is currently not
possible from within the m48t59 test). So we can only re-enable this
test on sparc, but not the sparc64 target.
Second, the fuzzing test is executed before the bcd-check-time test
(due to the naming of the tests), without having the base address set
up properly, so the fuzzing test does not really check anything at all.
Fix it by setting up the base address from the main function already
and by moving the qtest_start() to the tests themselves, so that each
test starts with a clean environment (since after the fuzzing, the clock
is unusable for the bcd-check-time test).
Signed-off-by: Thomas Huth <thuth@redhat.com>
Diffstat (limited to 'tests/i440fx-test.c')
0 files changed, 0 insertions, 0 deletions