hmp: Make json format optional for qom-set
PATCH v2 1/1 hmp: Make json format optional for qom-set
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 back to the previous handling and allow to specify passing json via the "-j" parameter.
---
v1 - v2:
- keep the "value:S" as correctly noted by Paolo :)
--- hmp-commands.hx | 7 ++++--- qom/qom-hmp-cmds.c | 20 ++++++++++++++++---- 2 files changed, 20 insertions(+), 7 deletions(-)
hmp-commands.hx +4 -3
@@ -1806,9 +1806,10 @@ ERST { .name = "qom-set", - .args_type = "path:s,property:s,value:S", - .params = "path property value", - .help = "set QOM property", + .args_type = "json:-j,path:s,property:s,value:S", + .params = "[-j] path property value", + .help = "set QOM property.\n\t\t\t" + "-j: the property is specified in json format.", .cmd = hmp_qom_set, .flags = "p", },
qom/qom-hmp-cmds.c +16 -4
@@ -44,15 +44,27 @@ void hmp_qom_list(Monitor *mon, const QDict *qdict)void hmp_qom_set (Monitor *mon,const QDict *qdict) { +const bool json =qdict_get_try_bool (qdict,"json" , false);const char *path =qdict_get_str (qdict,"path" );const char *property =qdict_get_str (qdict,"property" );const char *value =qdict_get_str (qdict,"value" );Error *err =NULL ; -QObject *obj; - obj =qobject_from_json (value, &err); -if (err ==NULL ) { -qmp_qom_set (path, property, obj, &err); +if (!json) { +Object *obj =object_resolve_path (path,NULL ); + +if (!obj) { +error_set (&err,ERROR_CLASS_DEVICE_NOT_FOUND , +"Device '%s' not found" , path); + }else { +object_property_parse (obj, value, property, &err); + } + }else { +QObject *obj =qobject_from_json (value, &err); + +if (!err) { +qmp_qom_set (path, property, obj, &err); + } }hmp_handle_error (mon, err);
Signature · 1 line
2.26.2
Quoted 28 lines · 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 back to the previous handling and allow to specify passing json via the "-j" parameter.
Cc Philippe Mathieu-Daudé <[email protected]>Cc Markus Armbruster <[email protected]>Cc Dr. David Alan Gilbert <[email protected]>Cc Paolo Bonzini <[email protected]>Cc "Daniel P. Berrangé" <[email protected]>Cc Eduardo Habkost <[email protected]>Signed-off-by David Hildenbrand <[email protected]>---
v1 - v2:
- keep the "value:S" as correctly noted by Paolo :)--- hmp-commands.hx | 7 ++++--- qom/qom-hmp-cmds.c | 20 ++++++++++++++++---- 2 files changed, 20 insertions(+), 7 deletions(-)hmp-commands.hx +0
-0
hmp-commands.hx ERST · line 1812
Quoted 10 lines
hmp-commands.hx +4
-3@@ -1806,9 +1806,10 @@ ERST { .name = "qom-set", - .args_type = "path:s,property:s,value:S", - .params = "path property value", - .help = "set QOM property", + .args_type = "json:-j,path:s,property:s,value:S", + .params = "[-j] path property value", + .help = "set QOM property.\n\t\t\t" + "-j: the property is specified in json format.",
Stupid mistake:
"-j: the value is specified in json format
Signature · 3 lines
Thanks, David / dhildenb
Quoted 8 lines · * David Hildenbrand ([email protected]) 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 use for properties that consume sizes.Let's switch back to the previous handling and allow to specify passing json via the "-j" parameter.
Quoted 7 lines
Cc Philippe Mathieu-Daudé <[email protected]>Cc Markus Armbruster <[email protected]>Cc Dr. David Alan Gilbert <[email protected]>Cc Paolo Bonzini <[email protected]>Cc "Daniel P. Berrangé" <[email protected]>Cc Eduardo Habkost <[email protected]>Signed-off-by David Hildenbrand <[email protected]>
Yep OK. Shame it's got back to even more complex but it makes sense.
Quoted 65 lines
---
v1 - v2:
- keep the "value:S" as correctly noted by Paolo :)--- hmp-commands.hx | 7 ++++--- qom/qom-hmp-cmds.c | 20 ++++++++++++++++---- 2 files changed, 20 insertions(+), 7 deletions(-)hmp-commands.hx +4
-3@@ -1806,9 +1806,10 @@ ERST { .name = "qom-set", - .args_type = "path:s,property:s,value:S", - .params = "path property value", - .help = "set QOM property", + .args_type = "json:-j,path:s,property:s,value:S", + .params = "[-j] path property value", + .help = "set QOM property.\n\t\t\t" + "-j: the property is specified in json format.", .cmd = hmp_qom_set, .flags = "p", },qom/qom-hmp-cmds.c +16
-4@@ -44,15 +44,27 @@ void hmp_qom_list(Monitor *mon, const QDict *qdict)void hmp_qom_set (Monitor *mon,const QDict *qdict) { +const bool json =qdict_get_try_bool (qdict,"json" , false);const char *path =qdict_get_str (qdict,"path" );const char *property =qdict_get_str (qdict,"property" );const char *value =qdict_get_str (qdict,"value" );Error *err =NULL ; -QObject *obj; - obj =qobject_from_json (value, &err); -if (err ==NULL ) { -qmp_qom_set (path, property, obj, &err); +if (!json) { +Object *obj =object_resolve_path (path,NULL ); + +if (!obj) { +error_set (&err,ERROR_CLASS_DEVICE_NOT_FOUND , +"Device '%s' not found" , path); + }else { +object_property_parse (obj, value, property, &err); + } + }else { +QObject *obj =qobject_from_json (value, &err); + +if (!err) { +qmp_qom_set (path, property, obj, &err); + } }hmp_handle_error (mon, err);Signature · 1 line
2.26.2
--
Dr. David Alan Gilbert / [email protected] / Manchester, UK
Quoted 42 lines · * David Hildenbrand ([email protected]) wrote:
Quoted 28 lines · 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 back to the previous handling and allow to specify passing json via the "-j" parameter.
Cc Philippe Mathieu-Daudé <[email protected]>Cc Markus Armbruster <[email protected]>Cc Dr. David Alan Gilbert <[email protected]>Cc Paolo Bonzini <[email protected]>Cc "Daniel P. Berrangé" <[email protected]>Cc Eduardo Habkost <[email protected]>Signed-off-by David Hildenbrand <[email protected]>---
v1 - v2:
- keep the "value:S" as correctly noted by Paolo :)--- hmp-commands.hx | 7 ++++--- qom/qom-hmp-cmds.c | 20 ++++++++++++++++---- 2 files changed, 20 insertions(+), 7 deletions(-)hmp-commands.hx +0
-0hmp-commands.hx ERST · line 1812
Quoted 10 lines
hmp-commands.hx +4
-3@@ -1806,9 +1806,10 @@ ERST { .name = "qom-set", - .args_type = "path:s,property:s,value:S", - .params = "path property value", - .help = "set QOM property", + .args_type = "json:-j,path:s,property:s,value:S", + .params = "[-j] path property value", + .help = "set QOM property.\n\t\t\t" + "-j: the property is specified in json format.",Stupid mistake:
Quoted 1 line
"-j: the value is specified in json format
oops; can fix that in commit
Quoted 5 lines
Signature · 4 lines
-- Thanks, David / dhildenb
--
Dr. David Alan Gilbert / [email protected] / Manchester, UK
Quoted 43 lines · Dr. David Alan Gilbert
Quoted 42 lines · * David Hildenbrand ([email protected]) wrote:
Quoted 28 lines · 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 back to the previous handling and allow to specify passing json via the "-j" parameter.
Cc Philippe Mathieu-Daudé <[email protected]>Cc Markus Armbruster <[email protected]>Cc Dr. David Alan Gilbert <[email protected]>Cc Paolo Bonzini <[email protected]>Cc "Daniel P. Berrangé" <[email protected]>Cc Eduardo Habkost <[email protected]>Signed-off-by David Hildenbrand <[email protected]>---
v1 - v2:
- keep the "value:S" as correctly noted by Paolo :)--- hmp-commands.hx | 7 ++++--- qom/qom-hmp-cmds.c | 20 ++++++++++++++++---- 2 files changed, 20 insertions(+), 7 deletions(-)hmp-commands.hx +0
-0hmp-commands.hx ERST · line 1812
Quoted 10 lines
hmp-commands.hx +4
-3@@ -1806,9 +1806,10 @@ ERST { .name = "qom-set", - .args_type = "path:s,property:s,value:S", - .params = "path property value", - .help = "set QOM property", + .args_type = "json:-j,path:s,property:s,value:S", + .params = "[-j] path property value", + .help = "set QOM property.\n\t\t\t" + "-j: the property is specified in json format.",Stupid mistake:
Quoted 3 lines
Quoted 1 line
"-j: the value is specified in json format
oops; can fix that in commit
Perfect, let me know in case you need a respin. Thanks!
Signature · 3 lines
Thanks, David / dhildenb
Quoted 7 lines · 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 back to the previous handling and allow to specify passing json via the "-j" parameter.
Two issues:
1. Makes qom-get and qom-set inconsistent
qom-get formats as JSON, always.
qom-set parses the string visitor's undocumented ad hoc language by default. You can make it parse JSON by passing -j.
Not a show stopper, but sure ugly. I feel documentation should point it out.
2. Rearms the string visitor death trap
If you try to qom-set a property whose ->set() uses something the string input visitor doesn't support, QEMU crashes. I'm not aware of such a ->set(), but this is a death trap all the same. Mind, I didn't actually *look* for such a ->set(). Details:
Subject: Re: [RFC PATCH] qom: Implement qom-get HMP command
Date: Sat, 02 May 2020 08:02:43 +0200 (6 weeks, 2 days, 4 minutes ago)
Message-ID: <[email protected]>
https://lists.nongnu.org/archive/html/qemu-devel/2020-05/msg00178.htmlSince we've had this death trap in the code for a number of years, I can't call its restoration a show stopper. It does feel like an unadvisable risk, though.
Quoted 10 lines · Markus Armbruster
Quoted 7 lines · 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 back to the previous handling and allow to specify passing json via the "-j" parameter.
Quoted 8 lines
Two issues:
1. Makes qom-get and qom-set inconsistent
qom-get formats as JSON, always.
qom-set parses the string visitor's undocumented ad hoc language by default. You can make it parse JSON by passing -j.
This is the same language the QEMU cmdline uses, no?
Quoted 3 lines
Not a show stopper, but sure ugly. I feel documentation should point it out.
Sure, we can fine-tune the documentation. For now we didn't have any qom-get users, in contrast to qom-set. Not sure if it makes sense to implement the same functionality for qom-get.
For now I can e.g.,
"echo "qom-set vm1 requested-size 256M" | sudo nc -U /var/tmp/mon_src"
then I can
echo "qom-get vm1 requested-size " | sudo nc -U /var/tmp/mon_src -> 268435456
which is a value I can punch back into qom-set. At least for sizes this works. Not perfect, not bad. Opinions?
Quoted 7 lines
2. Rearms the string visitor death trap
If you try to qom-set a property whose ->set() uses something the string input visitor doesn't support, QEMU crashes. I'm not aware of such a ->set(), but this is a death trap all the same. Mind, I didn't actually *look* for such a ->set(). Details:
Thanks. Maybe I am missing something important, but this sounds like we are missing a bunch of checks+errors. (wouldn't we be able to crash using the QEMU cmdline as well when setting such properties?).
Quoted 10 lines
Subject: Re: [RFC PATCH] qom: Implement qom-get HMP command Date: Sat, 02 May 2020 08:02:43 +0200 (6 weeks, 2 days, 4 minutes ago) Message-ID: <[email protected]> https://lists.nongnu.org/archive/html/qemu-devel/2020-05/msg00178.htmlSince we've had this death trap in the code for a number of years, I can't call its restoration a show stopper. It does feel like an unadvisable risk, though.
As long as there are no better alternatives to punch in data in the same format the QEMU cmdline consumes, I think this is perfectly reasonable. No good reason to make a HMP interface harder to use by humans IMHO.
Thanks!
Signature · 3 lines
Thanks, David / dhildenb
Quoted 14 lines · * Markus Armbruster ([email protected]) wrote:
Quoted 7 lines · 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 back to the previous handling and allow to specify passing json via the "-j" parameter.
Two issues:
1. Makes qom-get and qom-set inconsistent
Quoted 7 lines
qom-get formats as JSON, always.
qom-set parses the string visitor's undocumented ad hoc language by default. You can make it parse JSON by passing -j.
Not a show stopper, but sure ugly. I feel documentation should point it out.
I can imagine one way around this owuld be to remove the flag and make it happen in the failure case; i.e.:
obj = qobject_from_json(value, &err);
if (err == NULL) {
qmp_qom_set(path, property, obj, &err);
} else {
somehow check if it parses with the integer parser and if it
does use object_property_parse
}unfortunately that else path is a bit messy, because you need to pick a parser in this case and then if that fails probably present the json error message not it's error.
Quoted 7 lines
2. Rearms the string visitor death trap
If you try to qom-set a property whose ->set() uses something the string input visitor doesn't support, QEMU crashes. I'm not aware of such a ->set(), but this is a death trap all the same. Mind, I didn't actually *look* for such a ->set(). Details:
Quoted 8 lines
Subject: Re: [RFC PATCH] qom: Implement qom-get HMP command Date: Sat, 02 May 2020 08:02:43 +0200 (6 weeks, 2 days, 4 minutes ago) Message-ID: <[email protected]> https://lists.nongnu.org/archive/html/qemu-devel/2020-05/msg00178.htmlSince we've had this death trap in the code for a number of years, I can't call its restoration a show stopper. It does feel like an unadvisable risk, though.
That just needs fixing in qom somewhere; it shouldn't assert - people are too free with asserts.
Dave
--
Dr. David Alan Gilbert / [email protected] / Manchester, UK
Quoted 44 lines · * David Hildenbrand ([email protected]) wrote:
Quoted 43 lines · Dr. David Alan Gilbert
Quoted 42 lines · * David Hildenbrand ([email protected]) wrote:
Quoted 28 lines · 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 back to the previous handling and allow to specify passing json via the "-j" parameter.
Cc Philippe Mathieu-Daudé <[email protected]>Cc Markus Armbruster <[email protected]>Cc Dr. David Alan Gilbert <[email protected]>Cc Paolo Bonzini <[email protected]>Cc "Daniel P. Berrangé" <[email protected]>Cc Eduardo Habkost <[email protected]>Signed-off-by David Hildenbrand <[email protected]>---
v1 - v2:
- keep the "value:S" as correctly noted by Paolo :)--- hmp-commands.hx | 7 ++++--- qom/qom-hmp-cmds.c | 20 ++++++++++++++++---- 2 files changed, 20 insertions(+), 7 deletions(-)hmp-commands.hx +0
-0hmp-commands.hx ERST · line 1812
Quoted 10 lines
hmp-commands.hx +4
-3@@ -1806,9 +1806,10 @@ ERST { .name = "qom-set", - .args_type = "path:s,property:s,value:S", - .params = "path property value", - .help = "set QOM property", + .args_type = "json:-j,path:s,property:s,value:S", + .params = "[-j] path property value", + .help = "set QOM property.\n\t\t\t" + "-j: the property is specified in json format.",Stupid mistake:
Quoted 5 lines
Quoted 3 lines
Quoted 1 line
"-j: the value is specified in json format
oops; can fix that in commit
Perfect, let me know in case you need a respin. Thanks!
I've queued this; if we can come up with something nicer to meet Markus's suggestions that would be great, but for now we get the functionality back.
Quoted 7 lines
Signature · 4 lines
-- Thanks, David / dhildenb
--
Dr. David Alan Gilbert / [email protected] / Manchester, UK
Quoted 13 lines · David Hildenbrand
Quoted 12 lines · Markus Armbruster
Quoted 7 lines · 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 back to the previous handling and allow to specify passing json via the "-j" parameter.
Two issues:
Quoted 8 lines
Quoted 6 lines
1. Makes qom-get and qom-set inconsistent
qom-get formats as JSON, always.
qom-set parses the string visitor's undocumented ad hoc language by default. You can make it parse JSON by passing -j.
This is the same language the QEMU cmdline uses, no?
The CLI uses many, many languages. The string visitor's language may well be among them; can't tell offhand.
Quoted 13 lines
Quoted 4 lines
Not a show stopper, but sure ugly. I feel documentation should point it out.
Sure, we can fine-tune the documentation. For now we didn't have any qom-get users, in contrast to qom-set. Not sure if it makes sense to implement the same functionality for qom-get.
For now I can e.g.,
"echo "qom-set vm1 requested-size 256M" | sudo nc -U
/var/tmp/mon_src"
Quoted 7 lines
then I can
echo "qom-get vm1 requested-size " | sudo nc -U
/var/tmp/mon_src-> 268435456which is a value I can punch back into qom-set. At least for sizes this works. Not perfect, not bad. Opinions?
It happens to work in this case, because the JSON number returned by qom-get happens to get parsed the right way by qom-set.
Is this the case for all properties where qom-set isn't deadly due to issue 2.? Nobody knows.
Quoted 9 lines
Quoted 6 lines
2. Rearms the string visitor death trap
If you try to qom-set a property whose ->set() uses something the string input visitor doesn't support, QEMU crashes. I'm not aware of such a ->set(), but this is a death trap all the same. Mind, I didn't actually *look* for such a ->set(). Details:
Thanks. Maybe I am missing something important, but this sounds like we are missing a bunch of checks+errors.
The string visitor feels like a quick hack to get something that is human-friendly. It provides just enough functionality for its initial uses. The trouble is new uses that violate its restrictions are hard to spot.
In my opinion, what we're really missing a replacement of the ill-conceived string visitor. The less it's used, the better.
Since a replacement isn't being worked on, we may have to make it less dangerous to use. Patches welcome.
Quoted 2 lines
(wouldn't we be able to crash
using the QEMU cmdline as well when setting such properties?).
If the string visitor is used there. Nobody knows.
Quoted 5 lines
Quoted 5 lines
Subject: Re: [RFC PATCH] qom: Implement qom-get HMP command Date: Sat, 02 May 2020 08:02:43 +0200 (6 weeks, 2 days, 4 minutes ago) Message-ID: <[email protected]> https://lists.nongnu.org/archive/html/qemu-devel/2020-05/msg00178.html
Quoted 8 lines
Quoted 4 lines
Since we've had this death trap in the code for a number of years, I can't call its restoration a show stopper. It does feel like an unadvisable risk, though.
As long as there are no better alternatives to punch in data in the same format the QEMU cmdline consumes, I think this is perfectly reasonable. No good reason to make a HMP interface harder to use by humans IMHO.
Yes, HMP should be human-friendly. Not at any cost, though; I reiterate my conviction that this is an unadvisable risk.
A crash is the most unfriendly response of all.