diff options
author | Leonardo Bras <leobras@redhat.com> | 2022-06-20 02:39:45 -0300 |
---|---|---|
committer | Dr. David Alan Gilbert <dgilbert@redhat.com> | 2022-06-22 18:11:17 +0100 |
commit | 1abaec9a1b2c23f7aa94709a422128d9e42c3e0b (patch) | |
tree | 125d38fcdf0a5c9427a5ab3ebf4ab6b89f89be9d /io | |
parent | 4f5a09714c983a3471fd12e3c7f3196e95c650c1 (diff) | |
download | qemu-1abaec9a1b2c23f7aa94709a422128d9e42c3e0b.zip qemu-1abaec9a1b2c23f7aa94709a422128d9e42c3e0b.tar.gz qemu-1abaec9a1b2c23f7aa94709a422128d9e42c3e0b.tar.bz2 |
migration: Change zero_copy_send from migration parameter to migration capability
When originally implemented, zero_copy_send was designed as a Migration
paramenter.
But taking into account how is that supposed to work, and how
the difference between a capability and a parameter, it only makes sense
that zero-copy-send would work better as a capability.
Taking into account how recently the change got merged, it was decided
that it's still time to make it right, and convert zero_copy_send into
a Migration capability.
Signed-off-by: Leonardo Bras <leobras@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Acked-by: Markus Armbruster <armbru@redhat.com>
Acked-by: Peter Xu <peterx@redhat.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
dgilbert: always define the capability, even on non-Linux but error if
set; avoids build problems with the capability
Diffstat (limited to 'io')
0 files changed, 0 insertions, 0 deletions