Re: [Qemu-devel] [PATCH 2/3] migrate: Share common MigrationParameters struct

2016-10-17 Thread Eric Blake
On 09/08/2016 10:14 PM, Eric Blake wrote: > It is rather verbose, and slightly error-prone, to repeat > the same set of parameters for input (migrate-set-parameters) > as for output (query-migrate-parameters), where the only > difference is whether the members are optional. We can just > document

Re: [Qemu-devel] [PATCH 2/3] migrate: Share common MigrationParameters struct

2016-10-05 Thread Juan Quintela
Eric Blake wrote: > It is rather verbose, and slightly error-prone, to repeat > the same set of parameters for input (migrate-set-parameters) > as for output (query-migrate-parameters), where the only > difference is whether the members are optional. We can just > document that the optional membe

Re: [Qemu-devel] [PATCH 2/3] migrate: Share common MigrationParameters struct

2016-09-09 Thread Marc-André Lureau
On Fri, Sep 9, 2016 at 7:19 AM Eric Blake wrote: > It is rather verbose, and slightly error-prone, to repeat > the same set of parameters for input (migrate-set-parameters) > as for output (query-migrate-parameters), where the only > difference is whether the members are optional. We can just >

[Qemu-devel] [PATCH 2/3] migrate: Share common MigrationParameters struct

2016-09-08 Thread Eric Blake
It is rather verbose, and slightly error-prone, to repeat the same set of parameters for input (migrate-set-parameters) as for output (query-migrate-parameters), where the only difference is whether the members are optional. We can just document that the optional members will always be present on