| commit | ff64e0ba817d79968bffa88d205397abf05cc6e8 | |
| author | Avihai Horon <avihaih@nvidia.com> | |
| Mon, 4 Mar 2024 10:53:39 +0000 (4 12:53 +0200) | ||
| committer | Peter Xu <peterx@redhat.com> | |
| Mon, 11 Mar 2024 18:41:40 +0000 (11 14:41 -0400) | ||
| tree | c45d9cc30a4b564170f365fc643db848b0b9d08b | treesnapshot (tar.gz zip) |
| parent | 3f6ed59ec400a58646e766a323f7f8047f044b98 | commitdiff |
vfio/migration: Add a note about migration rate limiting
VFIO migration buffer size is currently limited to 1MB. Therefore, there
is no need to check if migration rate exceeded, as in the worst case it
will exceed by only 1MB.
However, if the buffer size is later changed to a bigger value,
vfio_save_iterate() should enforce migration rate (similar to migration
RAM code).
Add a note about this in vfio_save_iterate() to serve as a reminder.
Suggested-by: Peter Xu <peterx@redhat.com>
Signed-off-by: Avihai Horon <avihaih@nvidia.com>
Reviewed-by: Fabiano Rosas <farosas@suse.de>
Link: https://lore.kernel.org/r/20240304105339.20713-4-avihaih@nvidia.com
Signed-off-by: Peter Xu <peterx@redhat.com>
VFIO migration buffer size is currently limited to 1MB. Therefore, there
is no need to check if migration rate exceeded, as in the worst case it
will exceed by only 1MB.
However, if the buffer size is later changed to a bigger value,
vfio_save_iterate() should enforce migration rate (similar to migration
RAM code).
Add a note about this in vfio_save_iterate() to serve as a reminder.
Suggested-by: Peter Xu <peterx@redhat.com>
Signed-off-by: Avihai Horon <avihaih@nvidia.com>
Reviewed-by: Fabiano Rosas <farosas@suse.de>
Link: https://lore.kernel.org/r/20240304105339.20713-4-avihaih@nvidia.com
Signed-off-by: Peter Xu <peterx@redhat.com>
| hw/vfio/migration.c | diffblobblamehistory |