diff options
| author | Laszlo Ersek | 2013-11-29 18:12:20 +0100 |
|---|---|---|
| committer | Michael S. Tsirkin | 2013-12-23 12:12:34 +0100 |
| commit | c37805b6724e5d4c3ad41653630b72b43619474e (patch) | |
| tree | 9ebf6517aca8fefc65f7ecffb49088a7ebd90a5f /include/exec/exec-all.h | |
| parent | i440fx-test: qtest_start() should be paired with qtest_end() (diff) | |
| download | qemu-c37805b6724e5d4c3ad41653630b72b43619474e.tar.gz qemu-c37805b6724e5d4c3ad41653630b72b43619474e.tar.xz qemu-c37805b6724e5d4c3ad41653630b72b43619474e.zip | |
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>
Diffstat (limited to 'include/exec/exec-all.h')
0 files changed, 0 insertions, 0 deletions