Hi
This series move to options.c:
- all migration capabilities code
- all migration parameters code
- all properties code
- all qmp commands that only touch the previous
And once there:
- sort of functions
- make consistent and coherent all the functions naming/typing
- create accessors for the parameters/capabilties that don't exist
- more cleanups here and there.
Todo:
- There is still capabilities code on savevm.c, but I want this in
before moving that code to options.c, but still needs more thought
for my part. I.e. should I put vmstate sections in options.c, or
should I create new functions to access the capabilities in savevm.c.
Please review.