Hi,
I've added 'inline-fd:' proto to simplify migration to/from fd.
I thought about modifying the existing 'fd:' proto but I'm not sure it's a
good idea to change it's contract.
Existing 'fd:' proto works with previously added fd by getfd or add-fd commands.
If client doesn't want to work with this fd before or after migration then it's
easier to send an fd with the migrate-* command. Also, client shouldn't maintain
this fd.
Usage:
{ 'execute': 'migrate', 'arguments': { 'uri': 'inline-fd:' } }
{ 'execute': 'migrate-incoming', 'arguments': { 'uri': 'inline-fd:' } }
Regards,
Yury
Yury Kotov (3):
monitor: Add monitor_recv_fd function to work with sent fds
migration: Add inline-fd protocol
migration-test: Add a test for inline_fd protocol
include/monitor/monitor.h | 1 +
migration/Makefile.objs | 2 +-
migration/inline-fd.c | 89 ++++++++++++++++++++++
migration/inline-fd.h | 22 ++++++
migration/migration.c | 15 ++++
migration/trace-events | 4 +
monitor.c | 15 +++-
tests/libqtest.c | 83 +++++++++++++++++++-
tests/libqtest.h | 51 ++++++++++++-
tests/migration-test.c | 117 ++++++++++++++++++++++++++---
tests/qemu-seccomp | Bin 0 -> 1266168 bytes
tests/test-query-device-blockstats | Bin 0 -> 1272608 bytes
12 files changed, 379 insertions(+), 20 deletions(-)
create mode 100644 migration/inline-fd.c
create mode 100644 migration/inline-fd.h
create mode 100755 tests/qemu-seccomp
create mode 100755 tests/test-query-device-blockstats
--
2.21.0
