Re: [Qemu-devel] Re: [PATCH 1/2] Print asynchronous notifications on request

[Avi Kivity <avi@redhat.com>]

Jan Kiszka wrote:
> I understand the need, but the result looks a bit ugly, at least to
> humans forced to parse it. If you get this while in the middle of type a
> command... Moreover, is it impossible that such an async notification is
> issued while some other subsystem is already dumping a multi-line
> message to the monitor (using multiple prints)? That would be really
> problematic.
>   

No, unless that subsystem schedules between prints.

> But if this approach is merged, then I would really say we need
> separately configurable monitor terminals, 

No no please no

> and notify should then only
> affect the issuing one. However, my feeling is that a real
> machine-dedicated and easily processable channel would be better suited
> for this use case.
>   

Definitely.  Have a machine protocol with a strong emphasis on 
compatibility and parseability, and a human protocol with emphasis on 
friendliness (prompts, completions, fix typos).

-- 
error compiling committee.c: too many arguments to function