On Thu, Sep 09, 2021 at 06:48:21AM +0200, Markus Armbruster wrote:
> Daniel P. Berrangé writes:
>
> > On Wed, Sep 08, 2021 at 05:09:13PM +0200, Markus Armbruster wrote:
> >> Daniel P. Berrangé writes:
> >>
> >> > We are still adding HMP commands without any QMP counterparts. This is
> >> >
Markus Armbruster writes:
[...]
> Limitations:
>
> 1. If we convert a long-running HMP command to this technique, we print
>its output only after it completed its work. We also end up with a
>long-running QMP command, which is bad, because it stops the main
>loop and makes the QMP
On 08/09/21 17:09, Markus Armbruster wrote:
This is 77 out of 170 HMP commands. I was hoping for fewer.
There are several that are not quite 1:1, but still not HMP-specific.
exit_preconfig
This is x-exit-preconfig.
migrate_set_capability
migrate_set_parameter
These are
Daniel P. Berrangé writes:
> On Wed, Sep 08, 2021 at 05:09:13PM +0200, Markus Armbruster wrote:
>> Daniel P. Berrangé writes:
>>
>> > We are still adding HMP commands without any QMP counterparts. This is
>> > done because there are a reasonable number of scenarios where the cost
>> > of
On 9/8/21 5:09 PM, Markus Armbruster wrote:
> Daniel P. Berrangé writes:
>
>> We are still adding HMP commands without any QMP counterparts. This is
>> done because there are a reasonable number of scenarios where the cost
>> of designing a QAPI data type for the command is not justified.
>>
>>
On Wed, Sep 08, 2021 at 05:09:13PM +0200, Markus Armbruster wrote:
> Daniel P. Berrangé writes:
>
> > We are still adding HMP commands without any QMP counterparts. This is
> > done because there are a reasonable number of scenarios where the cost
> > of designing a QAPI data type for the
Daniel P. Berrangé writes:
> We are still adding HMP commands without any QMP counterparts. This is
> done because there are a reasonable number of scenarios where the cost
> of designing a QAPI data type for the command is not justified.
>
> This has the downside, however, that we will never be
On a Wednesday in 2021, Daniel P. Berrangé wrote:
We are still adding HMP commands without any QMP counterparts. This is
done because there are a reasonable number of scenarios where the cost
of designing a QAPI data type for the command is not justified.
This has the downside, however, that we
We are still adding HMP commands without any QMP counterparts. This is
done because there are a reasonable number of scenarios where the cost
of designing a QAPI data type for the command is not justified.
This has the downside, however, that we will never be able to fully
isolate the monitor
