02.12.2019, 23:50, "Markus Armbruster" :
> Yury Kotov writes:
>
>> Hi!
>>
>> 29.11.2019, 11:22, "Markus Armbruster" :
>>> Yury Kotov writes:
>>>
The monitor_can_read (as a callback of qemu_chr_fe_set_handlers)
should return size of buffer which monitor_qmp_read or monitor_read
>>
On 12/2/19 11:49 PM, Markus Armbruster wrote:
> Yury Kotov writes:
>
>> Hi!
>>
>> 29.11.2019, 11:22, "Markus Armbruster" :
>>> Yury Kotov writes:
>>>
The monitor_can_read (as a callback of qemu_chr_fe_set_handlers)
should return size of buffer which monitor_qmp_read or monitor_read
>>
Yury Kotov writes:
> Hi!
>
> 29.11.2019, 11:22, "Markus Armbruster" :
>> Yury Kotov writes:
>>
>>> The monitor_can_read (as a callback of qemu_chr_fe_set_handlers)
>>> should return size of buffer which monitor_qmp_read or monitor_read
>>> can process.
>>> Currently, monitor_can_read returns
Hi!
29.11.2019, 11:22, "Markus Armbruster" :
> Yury Kotov writes:
>
>> The monitor_can_read (as a callback of qemu_chr_fe_set_handlers)
>> should return size of buffer which monitor_qmp_read or monitor_read
>> can process.
>> Currently, monitor_can_read returns 1 as a result of logical not.
>
Yury Kotov writes:
> The monitor_can_read (as a callback of qemu_chr_fe_set_handlers)
> should return size of buffer which monitor_qmp_read or monitor_read
> can process.
> Currently, monitor_can_read returns 1 as a result of logical not.
> Thus, for each QMP command, len(QMD) iterations of the m
Cc'ing the chardev maintainers.
On 11/22/19 10:23 AM, Yury Kotov wrote:
The monitor_can_read (as a callback of qemu_chr_fe_set_handlers)
should return size of buffer which monitor_qmp_read or monitor_read
can process.
Currently, monitor_can_read returns 1 as a result of logical not.
Thus, for ea
The monitor_can_read (as a callback of qemu_chr_fe_set_handlers)
should return size of buffer which monitor_qmp_read or monitor_read
can process.
Currently, monitor_can_read returns 1 as a result of logical not.
Thus, for each QMP command, len(QMD) iterations of the main loop
are required to handle