Searched hist:"73581 a041e683fe7899e6af799c42becf60ee400" (Results 1 – 3 of 3) sorted by relevance
/openbmc/qemu/migration/ |
H A D | options.c | diff 73581a041e683fe7899e6af799c42becf60ee400 Thu Sep 19 08:46:22 CDT 2024 Fabiano Rosas <farosas@suse.de> migration: Deprecate zero-blocks capability
The zero-blocks capability was meant to be used along with the block migration, which has been removed already in commit eef0bae3a7 ("migration: Remove block migration").
Setting zero-blocks is currently a noop, but the outright removal of the capability would cause and error in case some users are still setting it. Put the capability through the deprecation process.
Signed-off-by: Fabiano Rosas <farosas@suse.de> Reviewed-by: Peter Xu <peterx@redhat.com> Link: https://lore.kernel.org/r/20240919134626.166183-4-dave@treblig.org Signed-off-by: Peter Xu <peterx@redhat.com>
|
/openbmc/qemu/qapi/ |
H A D | migration.json | diff 73581a041e683fe7899e6af799c42becf60ee400 Thu Sep 19 08:46:22 CDT 2024 Fabiano Rosas <farosas@suse.de> migration: Deprecate zero-blocks capability
The zero-blocks capability was meant to be used along with the block migration, which has been removed already in commit eef0bae3a7 ("migration: Remove block migration").
Setting zero-blocks is currently a noop, but the outright removal of the capability would cause and error in case some users are still setting it. Put the capability through the deprecation process.
Signed-off-by: Fabiano Rosas <farosas@suse.de> Reviewed-by: Peter Xu <peterx@redhat.com> Link: https://lore.kernel.org/r/20240919134626.166183-4-dave@treblig.org Signed-off-by: Peter Xu <peterx@redhat.com>
|
/openbmc/qemu/docs/about/ |
H A D | deprecated.rst | diff 73581a041e683fe7899e6af799c42becf60ee400 Thu Sep 19 08:46:22 CDT 2024 Fabiano Rosas <farosas@suse.de> migration: Deprecate zero-blocks capability
The zero-blocks capability was meant to be used along with the block migration, which has been removed already in commit eef0bae3a7 ("migration: Remove block migration").
Setting zero-blocks is currently a noop, but the outright removal of the capability would cause and error in case some users are still setting it. Put the capability through the deprecation process.
Signed-off-by: Fabiano Rosas <farosas@suse.de> Reviewed-by: Peter Xu <peterx@redhat.com> Link: https://lore.kernel.org/r/20240919134626.166183-4-dave@treblig.org Signed-off-by: Peter Xu <peterx@redhat.com>
|