Re: [PATCH v9 11/11] migration/virtio: Add virtio-gpu section

[Akihiko Odaki]

On 2024/04/26 0:45, Dmitry Osipenko wrote:
> Document virtio-gpu migration specifics.
>
> Suggested-by: Akihiko Odaki <akihiko.odaki@daynix.com>
> Signed-off-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
> ---
>   docs/devel/migration/virtio.rst | 7 +++++++
>   1 file changed, 7 insertions(+)
>
> diff --git a/docs/devel/migration/virtio.rst b/docs/devel/migration/virtio.rst
> index 611a18b82151..67f5fcfed196 100644
> --- a/docs/devel/migration/virtio.rst
> +++ b/docs/devel/migration/virtio.rst
> @@ -113,3 +113,10 @@ virtio_load() returned (like e.g. code depending on 
> features).
>   Any extension of the state being migrated should be done in subsections
>   added to the core for compatibility reasons. If transport or device specific
>   state is added, core needs to invoke a callback from the new subsection.
> +
> +VirtIO-GPU migration
> +====================
> +VirtIO-GPU doesn't adhere to a common virtio migration scheme. It doesn't
> +support save/loading of virtio device state, instead it uses generic device
> +migration management on top of the virtio core to save/load GPU state.
> +Migration of virgl and rutabaga states not supported.

Sorry for confusion, but I didn't mean to add a subsection to the 
documentation. I intended to refer to a terminology of migration data 
structure named subsection, which is documented at: 
docs/devel/migration/main.rst

A device-specific information is not worth to describe here.