SYS-OSS/FRET-qemu
4
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

migration: Improve example and documentation of vmstate_register()

Browse Source 
Reviewed-by: Stefan Berger <stefanb@linux.ibm.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
Message-ID: <20231020090731.28701-11-quintela@redhat.com>
This commit is contained in:
Juan Quintela 2023-10-20 11:07:28 +02:00
parent caa91b3c44
commit 5b146be3e7
1 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/devel/migration.rst
View File

@ -167,13 +167,17 @@ An example (from hw/input/pckbd.c)
} }
}; };
We are declaring the state with name "pckbd". We are declaring the state with name "pckbd". The ``version_id`` is
The ``version_id`` is 3, and the fields are 4 uint8_t in a KBDState structure. 3, and there are 4 uint8_t fields in the KBDState structure. We
We registered this with: registered this ``VMSTATEDescription`` with one of the following
functions. The first one will generate a device ``instance_id``
different for each registration. Use the second one if you already
have an id that is different for each instance of the device:
.. code:: c .. code:: c
vmstate_register(NULL, 0, &vmstate_kbd, s); vmstate_register_any(NULL, &vmstate_kbd, s);
vmstate_register(NULL, instance_id, &vmstate_kbd, s);
For devices that are ``qdev`` based, we can register the device in the class For devices that are ``qdev`` based, we can register the device in the class
init function: init function: