| commit | 83ff78e5674ccf01a2092c230c893cb2ef41a1a6 | |
| author | Christian Schoenebeck <qemu_oss@crudebyte.com> | |
| Tue, 26 Jan 2021 23:08:03 +0000 (27 00:08 +0100) | ||
| committer | Paolo Bonzini <pbonzini@redhat.com> | |
| Tue, 16 Feb 2021 16:15:39 +0000 (16 17:15 +0100) | ||
| tree | fc6dd4573cff5ebb441606194e4a812d7a7c81f7 | treesnapshot (tar.gz zip) |
| parent | 23820025af6b356cd4061a8b029c1126e1ee915e | commitdiff |
tests/qtest/qos-test: dump qos graph if verbose
If qtests were run in verbose mode (i.e. if --verbose CL argument was
provided) then dump the generated qos graph (all nodes and edges,
along with their current individual availability status) to stdout,
which allows to identify problems in the created qos graph e.g. when
writing new qos tests.
See API doc comment on function qos_dump_graph() for details.
Signed-off-by: Christian Schoenebeck <qemu_oss@crudebyte.com>
Message-Id: <6bffb6e38589fb2c06a2c1b5deed33f3e710fed1.1611704181.git.qemu_oss@crudebyte.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
If qtests were run in verbose mode (i.e. if --verbose CL argument was
provided) then dump the generated qos graph (all nodes and edges,
along with their current individual availability status) to stdout,
which allows to identify problems in the created qos graph e.g. when
writing new qos tests.
See API doc comment on function qos_dump_graph() for details.
Signed-off-by: Christian Schoenebeck <qemu_oss@crudebyte.com>
Message-Id: <6bffb6e38589fb2c06a2c1b5deed33f3e710fed1.1611704181.git.qemu_oss@crudebyte.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
| tests/qtest/libqos/qgraph.c | diffblobblamehistory | |
| tests/qtest/libqos/qgraph.h | diffblobblamehistory | |
| tests/qtest/qos-test.c | diffblobblamehistory |