514d00df5f
It turns out you can do this directly from Python ... and because of this, you don't need to worry about setting the inheritability of the fds or spawning another process. Doing this is helpful because it allows QEMUMonitorProtocol to keep its file descriptor and socket object as private implementation details. /that/ is helpful in turn because it allows me to write a compatible, alternative implementation. Signed-off-by: John Snow <jsnow@redhat.com> Reviewed-by: Hanna Reitz <hreitz@redhat.com> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com> Message-id: 20210923004938.3999963-10-jsnow@redhat.com Signed-off-by: John Snow <jsnow@redhat.com> |
||
|---|---|---|
| .. | ||
| README.rst | ||
| __init__.py | ||
| py.typed | ||
| qemu_ga_client.py | ||
| qmp_shell.py | ||
| qom.py | ||
| qom_common.py | ||
| qom_fuse.py | ||
README.rst
qemu.qmp package ================ This package provides a library used for connecting to and communicating with QMP servers. It is used extensively by iotests, vm tests, acceptance tests, and other utilities in the ./scripts directory. It is not a fully-fledged SDK and is subject to change at any time. See the documentation in ``__init__.py`` for more information.