| commit | 71daf640d91d49a784ead059c9021070a2107008 | |
| author | Juan Quintela <quintela@redhat.com> | |
| Fri, 20 Oct 2023 09:07:19 +0000 (20 11:07 +0200) | ||
| committer | Juan Quintela <quintela@redhat.com> | |
| Wed, 1 Nov 2023 15:13:58 +0000 (1 16:13 +0100) | ||
| tree | 768ab05d2c456e6510c698876667624303894a2a | treesnapshot (tar.gz zip) |
| parent | 832685707fbe52b2525974a100a240338998e544 | commitdiff |
migration: Create vmstate_register_any()
We have lots of cases where we are using an instance_id==0 when we
should be using VMSTATE_INSTANCE_ID_ANY (-1). Basically everything
that can have more than one needs to have a proper instance_id or -1
and the system will take one for it.
vmstate_register_any(): We register with -1.
Reviewed-by: Stefan Berger <stefanb@linux.ibm.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
Message-ID: <20231020090731.28701-2-quintela@redhat.com>
We have lots of cases where we are using an instance_id==0 when we
should be using VMSTATE_INSTANCE_ID_ANY (-1). Basically everything
that can have more than one needs to have a proper instance_id or -1
and the system will take one for it.
vmstate_register_any(): We register with -1.
Reviewed-by: Stefan Berger <stefanb@linux.ibm.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
Message-ID: <20231020090731.28701-2-quintela@redhat.com>
| include/migration/vmstate.h | diffblobblamehistory |