Laszlo Ersek c37805b672 i440fx-test: give each GTest case its own qtest
The current two GTest cases, /i440fx/defaults and /i440fx/pam can share a
qemu process, but the next two cases will need dedicated instances. It is
messy (and order-dependent) to dynamically configure GTest cases one by
one to start, stop, or keep the current qtest (*); let's just have each
GTest work with its own qtest. The performance difference should be
negligible.

(*) As g_test_run() can be invoked at most once per process startup, and
it runs GTest cases in sequence, we'd need clumsy data structures to
control each GTest case to start/stop/keep the qemu instance. Or, we'd
have to code the same information into the test methods themselves, which
would make them even more order-dependent.

Signed-off-by: Laszlo Ersek <lersek@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
2013-12-23 13:12:34 +02:00
2013-12-06 08:55:42 +01:00
2013-11-25 20:35:28 -08:00
2013-12-06 08:55:42 +01:00
2013-12-21 16:41:56 +01:00
2013-12-02 21:02:57 +04:00
2013-10-11 09:34:56 -07:00
2013-10-11 09:34:56 -07:00
2013-11-06 21:47:05 -08:00
2013-11-04 15:39:41 +02:00
2013-10-17 10:10:14 +02:00
2013-12-16 10:12:20 +01:00
2013-12-04 15:19:00 +01:00
2013-12-04 15:19:00 +01:00
2013-10-11 09:34:56 -07:00
2013-11-27 14:02:45 -08:00
2013-10-11 09:34:56 -07:00

Read the documentation in qemu-doc.html or on http://wiki.qemu-project.org

- QEMU team
Description
No description provided
Readme 404 MiB
Languages
C 82.6%
C++ 6.5%
Python 3.4%
Dylan 2.9%
Shell 1.6%
Other 2.8%