Cleber Rosa 8f8fd9edba Introduce a Python module structure ... This is a simple move of Python code that wraps common QEMU functionality, and are used by a number of different tests and scripts. By treating that code as a real Python module, we can more easily: * reuse code * have a proper place for the module's own unittests * apply a more consistent style * generate documentation Signed-off-by: Cleber Rosa <crosa@redhat.com> Reviewed-by: Caio Carrara <ccarrara@redhat.com> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com> Message-Id: <20190206162901.19082-2-crosa@redhat.com> Signed-off-by: Cleber Rosa <crosa@redhat.com>		2019-02-22 14:07:01 -05:00
..
__init__.py	tests: introduce a framework for testing migration performance	2016-07-22 13:23:39 +05:30
comparison.py	tests: introduce a framework for testing migration performance	2016-07-22 13:23:39 +05:30
engine.py	Introduce a Python module structure	2019-02-22 14:07:01 -05:00
hardware.py	tests: introduce a framework for testing migration performance	2016-07-22 13:23:39 +05:30
plot.py	python: futurize -f libfuturize.fixes.fix_print_with_import	2018-06-08 14:39:24 -03:00
progress.py	tests: introduce a framework for testing migration performance	2016-07-22 13:23:39 +05:30
report.py	tests: introduce a framework for testing migration performance	2016-07-22 13:23:39 +05:30
scenario.py	tests: introduce a framework for testing migration performance	2016-07-22 13:23:39 +05:30
shell.py	Revert "tests: migration/guestperf Python 2.6 argparse compatibility"	2018-10-03 23:08:51 -03:00
timings.py	tests: introduce a framework for testing migration performance	2016-07-22 13:23:39 +05:30