Re: [PATCH v7 3/5] migration: Add zero-copy parameter for QMP/HMP for Linux
Hello Juan, Thanks for thew feedback! On Fri, Feb 18, 2022 at 1:31 PM Juan Quintela wrote: > > Leonardo Bras Soares Passos wrote: > > On Wed, Jan 19, 2022 at 3:16 PM Daniel P. Berrangé > > wrote: > >> > >> On Wed, Jan 19, 2022 at 03:03:29PM -0300, Leonardo Bras Soares Passos > >> wrote: > >> > Hello Daniel, > >> > > >> > On Thu, Jan 13, 2022 at 10:10 AM Daniel P. Berrangé > >> > wrote: > >> > > > >> > > On Thu, Jan 06, 2022 at 07:13:40PM -0300, Leonardo Bras wrote: > >> > > > Add property that allows zero-copy migration of memory pages, > >> > > > and also includes a helper function migrate_use_zero_copy() to check > >> > > > if it's enabled. > >> > > > > >> > > > No code is introduced to actually do the migration, but it allow > >> > > > future implementations to enable/disable this feature. > >> > > > > >> > > > On non-Linux builds this parameter is compiled-out. > >> > > > > >> > > > Signed-off-by: Leonardo Bras > >> > > > --- > >> > > > qapi/migration.json | 24 > >> > > > migration/migration.h | 5 + > >> > > > migration/migration.c | 32 > >> > > > migration/socket.c| 5 + > >> > > > monitor/hmp-cmds.c| 6 ++ > >> > > > 5 files changed, 72 insertions(+) > >> > > > >> > > Reviewed-by: Daniel P. Berrangé > >> > > >> > Thanks! > >> > > > > Ok, I see the point. > > I will try to refactor the code changing zero-copy to zero-copy-send > > or something like that. > > Hi > > I am late to the party, but I agree with Dan that we need two flags. > > Thre reason is that you can be the target of one migration, and later be > the source of a next one. If we only have one flag that means different > things on the source and destination side, things become really > complicated. > > Later, Juan. > Yeah, that makes sense. :) Best regards, Leo
Re: [PATCH v7 3/5] migration: Add zero-copy parameter for QMP/HMP for Linux
Leonardo Bras Soares Passos wrote: > On Wed, Jan 19, 2022 at 3:16 PM Daniel P. Berrangé > wrote: >> >> On Wed, Jan 19, 2022 at 03:03:29PM -0300, Leonardo Bras Soares Passos wrote: >> > Hello Daniel, >> > >> > On Thu, Jan 13, 2022 at 10:10 AM Daniel P. Berrangé >> > wrote: >> > > >> > > On Thu, Jan 06, 2022 at 07:13:40PM -0300, Leonardo Bras wrote: >> > > > Add property that allows zero-copy migration of memory pages, >> > > > and also includes a helper function migrate_use_zero_copy() to check >> > > > if it's enabled. >> > > > >> > > > No code is introduced to actually do the migration, but it allow >> > > > future implementations to enable/disable this feature. >> > > > >> > > > On non-Linux builds this parameter is compiled-out. >> > > > >> > > > Signed-off-by: Leonardo Bras >> > > > --- >> > > > qapi/migration.json | 24 >> > > > migration/migration.h | 5 + >> > > > migration/migration.c | 32 >> > > > migration/socket.c| 5 + >> > > > monitor/hmp-cmds.c| 6 ++ >> > > > 5 files changed, 72 insertions(+) >> > > >> > > Reviewed-by: Daniel P. Berrangé >> > >> > Thanks! >> > > Ok, I see the point. > I will try to refactor the code changing zero-copy to zero-copy-send > or something like that. Hi I am late to the party, but I agree with Dan that we need two flags. Thre reason is that you can be the target of one migration, and later be the source of a next one. If we only have one flag that means different things on the source and destination side, things become really complicated. Later, Juan.
Re: [PATCH v7 3/5] migration: Add zero-copy parameter for QMP/HMP for Linux
On Wed, Jan 19, 2022 at 3:16 PM Daniel P. Berrangé wrote:
>
> On Wed, Jan 19, 2022 at 03:03:29PM -0300, Leonardo Bras Soares Passos wrote:
> > Hello Daniel,
> >
> > On Thu, Jan 13, 2022 at 10:10 AM Daniel P. Berrangé
> > wrote:
> > >
> > > On Thu, Jan 06, 2022 at 07:13:40PM -0300, Leonardo Bras wrote:
> > > > Add property that allows zero-copy migration of memory pages,
> > > > and also includes a helper function migrate_use_zero_copy() to check
> > > > if it's enabled.
> > > >
> > > > No code is introduced to actually do the migration, but it allow
> > > > future implementations to enable/disable this feature.
> > > >
> > > > On non-Linux builds this parameter is compiled-out.
> > > >
> > > > Signed-off-by: Leonardo Bras
> > > > ---
> > > > qapi/migration.json | 24
> > > > migration/migration.h | 5 +
> > > > migration/migration.c | 32
> > > > migration/socket.c| 5 +
> > > > monitor/hmp-cmds.c| 6 ++
> > > > 5 files changed, 72 insertions(+)
> > >
> > > Reviewed-by: Daniel P. Berrangé
> >
> > Thanks!
> >
> > >
> > > >
> > > > diff --git a/qapi/migration.json b/qapi/migration.json
> > > > index bbfd48cf0b..2e62ea6ebd 100644
> > > > --- a/qapi/migration.json
> > > > +++ b/qapi/migration.json
> > > > @@ -730,6 +730,13 @@
> > > > # will consume more CPU.
> > > > # Defaults to 1. (Since 5.0)
> > > > #
> > > > +# @zero-copy: Controls behavior on sending memory pages on migration.
> > > > +# When true, enables a zero-copy mechanism for sending
> > > > memory
> > > > +# pages, if host supports it.
> > > > +# Requires that QEMU be permitted to use locked memory for
> > > > guest
> > > > +# RAM pages.
> > > > +# Defaults to false. (Since 7.0)
> > > > +#
> > > > # @block-bitmap-mapping: Maps block nodes and bitmaps on them to
> > > > #aliases for the purpose of dirty bitmap
> > > > migration. Such
> > > > #aliases may for example be the corresponding
> > > > names on the
> > > > @@ -769,6 +776,7 @@
> > > > 'xbzrle-cache-size', 'max-postcopy-bandwidth',
> > > > 'max-cpu-throttle', 'multifd-compression',
> > > > 'multifd-zlib-level' ,'multifd-zstd-level',
> > > > + { 'name': 'zero-copy', 'if' : 'CONFIG_LINUX'},
> > > > 'block-bitmap-mapping' ] }
> > > >
> > > > ##
> > > > @@ -895,6 +903,13 @@
> > > > # will consume more CPU.
> > > > # Defaults to 1. (Since 5.0)
> > > > #
> > > > +# @zero-copy: Controls behavior on sending memory pages on migration.
> > > > +# When true, enables a zero-copy mechanism for sending
> > > > memory
> > > > +# pages, if host supports it.
> > > > +# Requires that QEMU be permitted to use locked memory for
> > > > guest
> > > > +# RAM pages.
> > > > +# Defaults to false. (Since 7.0)
> > > > +#
> > > > # @block-bitmap-mapping: Maps block nodes and bitmaps on them to
> > > > #aliases for the purpose of dirty bitmap
> > > > migration. Such
> > > > #aliases may for example be the corresponding
> > > > names on the
> > > > @@ -949,6 +964,7 @@
> > > > '*multifd-compression': 'MultiFDCompression',
> > > > '*multifd-zlib-level': 'uint8',
> > > > '*multifd-zstd-level': 'uint8',
> > > > +'*zero-copy': { 'type': 'bool', 'if': 'CONFIG_LINUX' },
> > > > '*block-bitmap-mapping': [ 'BitmapMigrationNodeAlias' ] } }
> > >
> > > The current zerocopy impl is for the send path.
> > >
> > > Do you expect we might get zerocopy in the receive path
> > > later ?
> >
> > It's possible, but I haven't started the implementation yet.
> >
> > >
> > > If so then either call this 'send-zero-copy', or change it
> > > from a bool to an enum taking '["send", "recv", "both"]'.
> > >
> > > I'd probably take the former and just rename it.
> > >
> >
> > Well, my rationale:
> > - I want to set zero copy sending:
> > zero-copy is set in the sending host, start migration.
> >
> > - I want to set zero copy receiving:
> > zero-copy is set in the receiving host, wait for migration.
> > (Of course host support is checked when setting the parameter).
> >
> > The problem with the current approach is trying to enable zero-copy on
> > receive before it's implemented, which will 'fail' silently .
> > A possible solution would be to add a patch to check in the receiving
> > path if zero-copy is enabled, and fail for now.
>
> That's not good because mgmt apps cannot query the QAPI schema
> to find out if this feature is supported or not.
>
> If we wantt o support zero copy recv, then we need an explicit
> flag for it that is distinct from zero copy send, so that apps
> can introspect whether the feature is
Re: [PATCH v7 3/5] migration: Add zero-copy parameter for QMP/HMP for Linux
On Wed, Jan 19, 2022 at 03:03:29PM -0300, Leonardo Bras Soares Passos wrote:
> Hello Daniel,
>
> On Thu, Jan 13, 2022 at 10:10 AM Daniel P. Berrangé
> wrote:
> >
> > On Thu, Jan 06, 2022 at 07:13:40PM -0300, Leonardo Bras wrote:
> > > Add property that allows zero-copy migration of memory pages,
> > > and also includes a helper function migrate_use_zero_copy() to check
> > > if it's enabled.
> > >
> > > No code is introduced to actually do the migration, but it allow
> > > future implementations to enable/disable this feature.
> > >
> > > On non-Linux builds this parameter is compiled-out.
> > >
> > > Signed-off-by: Leonardo Bras
> > > ---
> > > qapi/migration.json | 24
> > > migration/migration.h | 5 +
> > > migration/migration.c | 32
> > > migration/socket.c| 5 +
> > > monitor/hmp-cmds.c| 6 ++
> > > 5 files changed, 72 insertions(+)
> >
> > Reviewed-by: Daniel P. Berrangé
>
> Thanks!
>
> >
> > >
> > > diff --git a/qapi/migration.json b/qapi/migration.json
> > > index bbfd48cf0b..2e62ea6ebd 100644
> > > --- a/qapi/migration.json
> > > +++ b/qapi/migration.json
> > > @@ -730,6 +730,13 @@
> > > # will consume more CPU.
> > > # Defaults to 1. (Since 5.0)
> > > #
> > > +# @zero-copy: Controls behavior on sending memory pages on migration.
> > > +# When true, enables a zero-copy mechanism for sending memory
> > > +# pages, if host supports it.
> > > +# Requires that QEMU be permitted to use locked memory for
> > > guest
> > > +# RAM pages.
> > > +# Defaults to false. (Since 7.0)
> > > +#
> > > # @block-bitmap-mapping: Maps block nodes and bitmaps on them to
> > > #aliases for the purpose of dirty bitmap
> > > migration. Such
> > > #aliases may for example be the corresponding
> > > names on the
> > > @@ -769,6 +776,7 @@
> > > 'xbzrle-cache-size', 'max-postcopy-bandwidth',
> > > 'max-cpu-throttle', 'multifd-compression',
> > > 'multifd-zlib-level' ,'multifd-zstd-level',
> > > + { 'name': 'zero-copy', 'if' : 'CONFIG_LINUX'},
> > > 'block-bitmap-mapping' ] }
> > >
> > > ##
> > > @@ -895,6 +903,13 @@
> > > # will consume more CPU.
> > > # Defaults to 1. (Since 5.0)
> > > #
> > > +# @zero-copy: Controls behavior on sending memory pages on migration.
> > > +# When true, enables a zero-copy mechanism for sending memory
> > > +# pages, if host supports it.
> > > +# Requires that QEMU be permitted to use locked memory for
> > > guest
> > > +# RAM pages.
> > > +# Defaults to false. (Since 7.0)
> > > +#
> > > # @block-bitmap-mapping: Maps block nodes and bitmaps on them to
> > > #aliases for the purpose of dirty bitmap
> > > migration. Such
> > > #aliases may for example be the corresponding
> > > names on the
> > > @@ -949,6 +964,7 @@
> > > '*multifd-compression': 'MultiFDCompression',
> > > '*multifd-zlib-level': 'uint8',
> > > '*multifd-zstd-level': 'uint8',
> > > +'*zero-copy': { 'type': 'bool', 'if': 'CONFIG_LINUX' },
> > > '*block-bitmap-mapping': [ 'BitmapMigrationNodeAlias' ] } }
> >
> > The current zerocopy impl is for the send path.
> >
> > Do you expect we might get zerocopy in the receive path
> > later ?
>
> It's possible, but I haven't started the implementation yet.
>
> >
> > If so then either call this 'send-zero-copy', or change it
> > from a bool to an enum taking '["send", "recv", "both"]'.
> >
> > I'd probably take the former and just rename it.
> >
>
> Well, my rationale:
> - I want to set zero copy sending:
> zero-copy is set in the sending host, start migration.
>
> - I want to set zero copy receiving:
> zero-copy is set in the receiving host, wait for migration.
> (Of course host support is checked when setting the parameter).
>
> The problem with the current approach is trying to enable zero-copy on
> receive before it's implemented, which will 'fail' silently .
> A possible solution would be to add a patch to check in the receiving
> path if zero-copy is enabled, and fail for now.
That's not good because mgmt apps cannot query the QAPI schema
to find out if this feature is supported or not.
If we wantt o support zero copy recv, then we need an explicit
flag for it that is distinct from zero copy send, so that apps
can introspect whether the feature is implemneted in QEMU or
not.
Distinct named bool flags feels better, and also makes it clear
to anyone not familiar with the impl that the current code is
strictly send only.
Regards,
Daniel
--
|: https://berrange.com -o-https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o-
Re: [PATCH v7 3/5] migration: Add zero-copy parameter for QMP/HMP for Linux
Hello Daniel,
On Thu, Jan 13, 2022 at 10:10 AM Daniel P. Berrangé wrote:
>
> On Thu, Jan 06, 2022 at 07:13:40PM -0300, Leonardo Bras wrote:
> > Add property that allows zero-copy migration of memory pages,
> > and also includes a helper function migrate_use_zero_copy() to check
> > if it's enabled.
> >
> > No code is introduced to actually do the migration, but it allow
> > future implementations to enable/disable this feature.
> >
> > On non-Linux builds this parameter is compiled-out.
> >
> > Signed-off-by: Leonardo Bras
> > ---
> > qapi/migration.json | 24
> > migration/migration.h | 5 +
> > migration/migration.c | 32
> > migration/socket.c| 5 +
> > monitor/hmp-cmds.c| 6 ++
> > 5 files changed, 72 insertions(+)
>
> Reviewed-by: Daniel P. Berrangé
Thanks!
>
> >
> > diff --git a/qapi/migration.json b/qapi/migration.json
> > index bbfd48cf0b..2e62ea6ebd 100644
> > --- a/qapi/migration.json
> > +++ b/qapi/migration.json
> > @@ -730,6 +730,13 @@
> > # will consume more CPU.
> > # Defaults to 1. (Since 5.0)
> > #
> > +# @zero-copy: Controls behavior on sending memory pages on migration.
> > +# When true, enables a zero-copy mechanism for sending memory
> > +# pages, if host supports it.
> > +# Requires that QEMU be permitted to use locked memory for
> > guest
> > +# RAM pages.
> > +# Defaults to false. (Since 7.0)
> > +#
> > # @block-bitmap-mapping: Maps block nodes and bitmaps on them to
> > #aliases for the purpose of dirty bitmap
> > migration. Such
> > #aliases may for example be the corresponding
> > names on the
> > @@ -769,6 +776,7 @@
> > 'xbzrle-cache-size', 'max-postcopy-bandwidth',
> > 'max-cpu-throttle', 'multifd-compression',
> > 'multifd-zlib-level' ,'multifd-zstd-level',
> > + { 'name': 'zero-copy', 'if' : 'CONFIG_LINUX'},
> > 'block-bitmap-mapping' ] }
> >
> > ##
> > @@ -895,6 +903,13 @@
> > # will consume more CPU.
> > # Defaults to 1. (Since 5.0)
> > #
> > +# @zero-copy: Controls behavior on sending memory pages on migration.
> > +# When true, enables a zero-copy mechanism for sending memory
> > +# pages, if host supports it.
> > +# Requires that QEMU be permitted to use locked memory for
> > guest
> > +# RAM pages.
> > +# Defaults to false. (Since 7.0)
> > +#
> > # @block-bitmap-mapping: Maps block nodes and bitmaps on them to
> > #aliases for the purpose of dirty bitmap
> > migration. Such
> > #aliases may for example be the corresponding
> > names on the
> > @@ -949,6 +964,7 @@
> > '*multifd-compression': 'MultiFDCompression',
> > '*multifd-zlib-level': 'uint8',
> > '*multifd-zstd-level': 'uint8',
> > +'*zero-copy': { 'type': 'bool', 'if': 'CONFIG_LINUX' },
> > '*block-bitmap-mapping': [ 'BitmapMigrationNodeAlias' ] } }
>
> The current zerocopy impl is for the send path.
>
> Do you expect we might get zerocopy in the receive path
> later ?
It's possible, but I haven't started the implementation yet.
>
> If so then either call this 'send-zero-copy', or change it
> from a bool to an enum taking '["send", "recv", "both"]'.
>
> I'd probably take the former and just rename it.
>
Well, my rationale:
- I want to set zero copy sending:
zero-copy is set in the sending host, start migration.
- I want to set zero copy receiving:
zero-copy is set in the receiving host, wait for migration.
(Of course host support is checked when setting the parameter).
The problem with the current approach is trying to enable zero-copy on
receive before it's implemented, which will 'fail' silently .
A possible solution would be to add a patch to check in the receiving
path if zero-copy is enabled, and fail for now.
What do you think?
Best regards,
Leo
>
> Regards,
> Daniel
> --
> |: https://berrange.com -o-https://www.flickr.com/photos/dberrange :|
> |: https://libvirt.org -o-https://fstop138.berrange.com :|
> |: https://entangle-photo.org-o-https://www.instagram.com/dberrange :|
>
Re: [PATCH v7 3/5] migration: Add zero-copy parameter for QMP/HMP for Linux
Hello Peter,
On Thu, Jan 13, 2022 at 4:00 AM Peter Xu wrote:
>
> On Thu, Jan 06, 2022 at 07:13:40PM -0300, Leonardo Bras wrote:
> > Add property that allows zero-copy migration of memory pages,
> > and also includes a helper function migrate_use_zero_copy() to check
> > if it's enabled.
> >
> > No code is introduced to actually do the migration, but it allow
> > future implementations to enable/disable this feature.
> >
> > On non-Linux builds this parameter is compiled-out.
>
> I feel sad every time seeing a new parameter needs to be mostly duplicated 3
> times in the code. :(
>
> > diff --git a/migration/socket.c b/migration/socket.c
> > index 05705a32d8..f7a77aafd3 100644
> > --- a/migration/socket.c
> > +++ b/migration/socket.c
> > @@ -77,6 +77,11 @@ static void socket_outgoing_migration(QIOTask *task,
> > } else {
> > trace_migration_socket_outgoing_connected(data->hostname);
> > }
> > +
> > +if (migrate_use_zero_copy()) {
> > +error_setg(, "Zero copy not available in migration");
> > +}
>
> I got confused the 1st time looking at it.. I think this is not strongly
> needed, but that's okay:
The idea is to avoid some future issues on testing migration while bisecting.
>
> Reviewed-by: Peter Xu
Thanks Peter!
>
> Thanks,
>
> --
> Peter Xu
>
Re: [PATCH v7 3/5] migration: Add zero-copy parameter for QMP/HMP for Linux
On Thu, Jan 06, 2022 at 07:13:40PM -0300, Leonardo Bras wrote:
> Add property that allows zero-copy migration of memory pages,
> and also includes a helper function migrate_use_zero_copy() to check
> if it's enabled.
>
> No code is introduced to actually do the migration, but it allow
> future implementations to enable/disable this feature.
>
> On non-Linux builds this parameter is compiled-out.
>
> Signed-off-by: Leonardo Bras
> ---
> qapi/migration.json | 24
> migration/migration.h | 5 +
> migration/migration.c | 32
> migration/socket.c| 5 +
> monitor/hmp-cmds.c| 6 ++
> 5 files changed, 72 insertions(+)
Reviewed-by: Daniel P. Berrangé
>
> diff --git a/qapi/migration.json b/qapi/migration.json
> index bbfd48cf0b..2e62ea6ebd 100644
> --- a/qapi/migration.json
> +++ b/qapi/migration.json
> @@ -730,6 +730,13 @@
> # will consume more CPU.
> # Defaults to 1. (Since 5.0)
> #
> +# @zero-copy: Controls behavior on sending memory pages on migration.
> +# When true, enables a zero-copy mechanism for sending memory
> +# pages, if host supports it.
> +# Requires that QEMU be permitted to use locked memory for guest
> +# RAM pages.
> +# Defaults to false. (Since 7.0)
> +#
> # @block-bitmap-mapping: Maps block nodes and bitmaps on them to
> #aliases for the purpose of dirty bitmap migration.
> Such
> #aliases may for example be the corresponding names
> on the
> @@ -769,6 +776,7 @@
> 'xbzrle-cache-size', 'max-postcopy-bandwidth',
> 'max-cpu-throttle', 'multifd-compression',
> 'multifd-zlib-level' ,'multifd-zstd-level',
> + { 'name': 'zero-copy', 'if' : 'CONFIG_LINUX'},
> 'block-bitmap-mapping' ] }
>
> ##
> @@ -895,6 +903,13 @@
> # will consume more CPU.
> # Defaults to 1. (Since 5.0)
> #
> +# @zero-copy: Controls behavior on sending memory pages on migration.
> +# When true, enables a zero-copy mechanism for sending memory
> +# pages, if host supports it.
> +# Requires that QEMU be permitted to use locked memory for guest
> +# RAM pages.
> +# Defaults to false. (Since 7.0)
> +#
> # @block-bitmap-mapping: Maps block nodes and bitmaps on them to
> #aliases for the purpose of dirty bitmap migration.
> Such
> #aliases may for example be the corresponding names
> on the
> @@ -949,6 +964,7 @@
> '*multifd-compression': 'MultiFDCompression',
> '*multifd-zlib-level': 'uint8',
> '*multifd-zstd-level': 'uint8',
> +'*zero-copy': { 'type': 'bool', 'if': 'CONFIG_LINUX' },
> '*block-bitmap-mapping': [ 'BitmapMigrationNodeAlias' ] } }
The current zerocopy impl is for the send path.
Do you expect we might get zerocopy in the receive path
later ?
If so then either call this 'send-zero-copy', or change it
from a bool to an enum taking '["send", "recv", "both"]'.
I'd probably take the former and just rename it.
Regards,
Daniel
--
|: https://berrange.com -o-https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o-https://fstop138.berrange.com :|
|: https://entangle-photo.org-o-https://www.instagram.com/dberrange :|
Re: [PATCH v7 3/5] migration: Add zero-copy parameter for QMP/HMP for Linux
On Thu, Jan 06, 2022 at 07:13:40PM -0300, Leonardo Bras wrote:
> Add property that allows zero-copy migration of memory pages,
> and also includes a helper function migrate_use_zero_copy() to check
> if it's enabled.
>
> No code is introduced to actually do the migration, but it allow
> future implementations to enable/disable this feature.
>
> On non-Linux builds this parameter is compiled-out.
I feel sad every time seeing a new parameter needs to be mostly duplicated 3
times in the code. :(
> diff --git a/migration/socket.c b/migration/socket.c
> index 05705a32d8..f7a77aafd3 100644
> --- a/migration/socket.c
> +++ b/migration/socket.c
> @@ -77,6 +77,11 @@ static void socket_outgoing_migration(QIOTask *task,
> } else {
> trace_migration_socket_outgoing_connected(data->hostname);
> }
> +
> +if (migrate_use_zero_copy()) {
> +error_setg(, "Zero copy not available in migration");
> +}
I got confused the 1st time looking at it.. I think this is not strongly
needed, but that's okay:
Reviewed-by: Peter Xu
Thanks,
--
Peter Xu
[PATCH v7 3/5] migration: Add zero-copy parameter for QMP/HMP for Linux
Add property that allows zero-copy migration of memory pages,
and also includes a helper function migrate_use_zero_copy() to check
if it's enabled.
No code is introduced to actually do the migration, but it allow
future implementations to enable/disable this feature.
On non-Linux builds this parameter is compiled-out.
Signed-off-by: Leonardo Bras
---
qapi/migration.json | 24
migration/migration.h | 5 +
migration/migration.c | 32
migration/socket.c| 5 +
monitor/hmp-cmds.c| 6 ++
5 files changed, 72 insertions(+)
diff --git a/qapi/migration.json b/qapi/migration.json
index bbfd48cf0b..2e62ea6ebd 100644
--- a/qapi/migration.json
+++ b/qapi/migration.json
@@ -730,6 +730,13 @@
# will consume more CPU.
# Defaults to 1. (Since 5.0)
#
+# @zero-copy: Controls behavior on sending memory pages on migration.
+# When true, enables a zero-copy mechanism for sending memory
+# pages, if host supports it.
+# Requires that QEMU be permitted to use locked memory for guest
+# RAM pages.
+# Defaults to false. (Since 7.0)
+#
# @block-bitmap-mapping: Maps block nodes and bitmaps on them to
#aliases for the purpose of dirty bitmap migration.
Such
#aliases may for example be the corresponding names on
the
@@ -769,6 +776,7 @@
'xbzrle-cache-size', 'max-postcopy-bandwidth',
'max-cpu-throttle', 'multifd-compression',
'multifd-zlib-level' ,'multifd-zstd-level',
+ { 'name': 'zero-copy', 'if' : 'CONFIG_LINUX'},
'block-bitmap-mapping' ] }
##
@@ -895,6 +903,13 @@
# will consume more CPU.
# Defaults to 1. (Since 5.0)
#
+# @zero-copy: Controls behavior on sending memory pages on migration.
+# When true, enables a zero-copy mechanism for sending memory
+# pages, if host supports it.
+# Requires that QEMU be permitted to use locked memory for guest
+# RAM pages.
+# Defaults to false. (Since 7.0)
+#
# @block-bitmap-mapping: Maps block nodes and bitmaps on them to
#aliases for the purpose of dirty bitmap migration.
Such
#aliases may for example be the corresponding names on
the
@@ -949,6 +964,7 @@
'*multifd-compression': 'MultiFDCompression',
'*multifd-zlib-level': 'uint8',
'*multifd-zstd-level': 'uint8',
+'*zero-copy': { 'type': 'bool', 'if': 'CONFIG_LINUX' },
'*block-bitmap-mapping': [ 'BitmapMigrationNodeAlias' ] } }
##
@@ -1095,6 +,13 @@
# will consume more CPU.
# Defaults to 1. (Since 5.0)
#
+# @zero-copy: Controls behavior on sending memory pages on migration.
+# When true, enables a zero-copy mechanism for sending memory
+# pages, if host supports it.
+# Requires that QEMU be permitted to use locked memory for guest
+# RAM pages.
+# Defaults to false. (Since 7.0)
+#
# @block-bitmap-mapping: Maps block nodes and bitmaps on them to
#aliases for the purpose of dirty bitmap migration.
Such
#aliases may for example be the corresponding names on
the
@@ -1147,6 +1170,7 @@
'*multifd-compression': 'MultiFDCompression',
'*multifd-zlib-level': 'uint8',
'*multifd-zstd-level': 'uint8',
+'*zero-copy': { 'type': 'bool', 'if': 'CONFIG_LINUX' },
'*block-bitmap-mapping': [ 'BitmapMigrationNodeAlias' ] } }
##
diff --git a/migration/migration.h b/migration/migration.h
index 8130b703eb..1489eeb165 100644
--- a/migration/migration.h
+++ b/migration/migration.h
@@ -339,6 +339,11 @@ MultiFDCompression migrate_multifd_compression(void);
int migrate_multifd_zlib_level(void);
int migrate_multifd_zstd_level(void);
+#ifdef CONFIG_LINUX
+bool migrate_use_zero_copy(void);
+#else
+#define migrate_use_zero_copy() (false)
+#endif
int migrate_use_xbzrle(void);
uint64_t migrate_xbzrle_cache_size(void);
bool migrate_colo_enabled(void);
diff --git a/migration/migration.c b/migration/migration.c
index 0652165610..aa8f1dc835 100644
--- a/migration/migration.c
+++ b/migration/migration.c
@@ -893,6 +893,10 @@ MigrationParameters *qmp_query_migrate_parameters(Error
**errp)
params->multifd_zlib_level = s->parameters.multifd_zlib_level;
params->has_multifd_zstd_level = true;
params->multifd_zstd_level = s->parameters.multifd_zstd_level;
+#ifdef CONFIG_LINUX
+params->has_zero_copy = true;
+params->zero_copy = s->parameters.zero_copy;
+#endif
params->has_xbzrle_cache_size = true;
params->xbzrle_cache_size = s->parameters.xbzrle_cache_size;
params->has_max_postcopy_bandwidth = true;
@@
