[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Making QEMU easier for management tools and applications

From: Paolo Bonzini
Subject: Re: Making QEMU easier for management tools and applications
Date: Fri, 31 Jan 2020 08:48:03 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.1

On 31/01/20 07:50, Markus Armbruster wrote:
>>> Consider chardev-add.  Example:
>>>     {"execute": "chardev-add",
>>>      "arguments": {"id": "bar",
>>>                    "backend": {"type": "file",
>>>                                "data": {"out": "/tmp/bar.log"}}}}
>>> The arguments as dotted keys:
>>>     id=bar,backend.type=file,backend.data.out=/tmp/bar.log
>>> Observe there's quite some of nesting.  While that's somewhat cumbersome
>>> in JSON, it's a lot worse with dotted keys, because there nesting means
>>> repeated key prefixes.  I could give much worse examples, actually.
>> This is true, but even without the repeated keys (e.g. in a syntax that
>> would use brackets), it would still be unnecessarily verbose and
>> probably hard to remember:
>>     id=bar,backend={type=file,data={out=/tmp/bar.log}}
> No argument.  It's unnecessarily verbose in JSON, too.

I think we should be able to switch chardevs to -object/object_add these
days.  Not right now, but it may be possible.  Introducing a warning
when chardev and object ids conflict would be a start.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]