On Fri, 9 Aug 2019 at 11:29, Damien Hedde <damien.he...@greensocs.com> wrote: > > One way to keep the feature without copy-pasting vmsd would be to add > a new vmstate_register with an additional argument to pass the base > class vmsd section and handle the whole thing there.
If we have a vmstate section which contains no actual data, only subsections with 'needed' functions, is it migration compatible with previous versions in the same way that tacking a subsection onto an existing function is? thanks -- PMM
