Re: [PATCH v2] hmp: Make json format optional for qom-set

2020-06-22 Thread Markus Armbruster
David Hildenbrand writes: > On 15.06.20 08:17, Markus Armbruster wrote: >> David Hildenbrand writes: >> >>> Commit 7d2ef6dcc1cf ("hmp: Simplify qom-set") switched to the json >>> parser, making it possible to specify complex types. However, with this >>> change it is no longer possible to speci

Re: [PATCH v2] hmp: Make json format optional for qom-set

2020-06-17 Thread Dr. David Alan Gilbert
* David Hildenbrand (da...@redhat.com) wrote: > On 10.06.20 12:39, Dr. David Alan Gilbert wrote: > > * David Hildenbrand (da...@redhat.com) wrote: > >> On 10.06.20 09:51, David Hildenbrand wrote: > >>> Commit 7d2ef6dcc1cf ("hmp: Simplify qom-set") switched to the json > >>> parser, making it possib

Re: [PATCH v2] hmp: Make json format optional for qom-set

2020-06-15 Thread Dr. David Alan Gilbert
* Markus Armbruster (arm...@redhat.com) wrote: > David Hildenbrand writes: > > > Commit 7d2ef6dcc1cf ("hmp: Simplify qom-set") switched to the json > > parser, making it possible to specify complex types. However, with this > > change it is no longer possible to specify proper sizes (e.g., 2G, 12

Re: [PATCH v2] hmp: Make json format optional for qom-set

2020-06-15 Thread David Hildenbrand
On 15.06.20 08:17, Markus Armbruster wrote: > David Hildenbrand writes: > >> Commit 7d2ef6dcc1cf ("hmp: Simplify qom-set") switched to the json >> parser, making it possible to specify complex types. However, with this >> change it is no longer possible to specify proper sizes (e.g., 2G, 128M), >

Re: [PATCH v2] hmp: Make json format optional for qom-set

2020-06-14 Thread Markus Armbruster
David Hildenbrand writes: > Commit 7d2ef6dcc1cf ("hmp: Simplify qom-set") switched to the json > parser, making it possible to specify complex types. However, with this > change it is no longer possible to specify proper sizes (e.g., 2G, 128M), > turning the interface harder to use for properties

Re: [PATCH v2] hmp: Make json format optional for qom-set

2020-06-10 Thread David Hildenbrand
On 10.06.20 12:39, Dr. David Alan Gilbert wrote: > * David Hildenbrand (da...@redhat.com) wrote: >> On 10.06.20 09:51, David Hildenbrand wrote: >>> Commit 7d2ef6dcc1cf ("hmp: Simplify qom-set") switched to the json >>> parser, making it possible to specify complex types. However, with this >>> chan

Re: [PATCH v2] hmp: Make json format optional for qom-set

2020-06-10 Thread Dr. David Alan Gilbert
* David Hildenbrand (da...@redhat.com) wrote: > On 10.06.20 09:51, David Hildenbrand wrote: > > Commit 7d2ef6dcc1cf ("hmp: Simplify qom-set") switched to the json > > parser, making it possible to specify complex types. However, with this > > change it is no longer possible to specify proper sizes

Re: [PATCH v2] hmp: Make json format optional for qom-set

2020-06-10 Thread Dr. David Alan Gilbert
* David Hildenbrand (da...@redhat.com) wrote: > Commit 7d2ef6dcc1cf ("hmp: Simplify qom-set") switched to the json > parser, making it possible to specify complex types. However, with this > change it is no longer possible to specify proper sizes (e.g., 2G, 128M), > turning the interface harder to

Re: [PATCH v2] hmp: Make json format optional for qom-set

2020-06-10 Thread David Hildenbrand
On 10.06.20 09:51, David Hildenbrand wrote: > Commit 7d2ef6dcc1cf ("hmp: Simplify qom-set") switched to the json > parser, making it possible to specify complex types. However, with this > change it is no longer possible to specify proper sizes (e.g., 2G, 128M), > turning the interface harder to us

[PATCH v2] hmp: Make json format optional for qom-set

2020-06-10 Thread David Hildenbrand
Commit 7d2ef6dcc1cf ("hmp: Simplify qom-set") switched to the json parser, making it possible to specify complex types. However, with this change it is no longer possible to specify proper sizes (e.g., 2G, 128M), turning the interface harder to use for properties that consume sizes. Let's switch b