Re: [Qemu-devel] Re: [RFD] virtio: Add memory statistics reporting to the balloon driver

[Luiz Capitulino <lcapitulino@redhat.com>]

On Fri, 08 Jan 2010 10:31:28 -0600
Anthony Liguori <anthony@codemonkey.ws> wrote:

> On 01/07/2010 12:30 PM, Luiz Capitulino wrote:
> > On Thu, 7 Jan 2010 15:58:30 -0200
> > Luiz Capitulino<lcapitulino@redhat.com>  wrote:
> >
> >    
> >>   I like Daniel's idea too. In practice 'refresh-balloon' is going to
> >> be Anthony's idea #1 for the QMP case, which seems the right way to
> >> do it with QMP.
> >>      
> >   Hm, something that has just occurred to me: it's easy to have
> > async messages in the user Monitor, we could add a new type of
> > user print callback called async_print.
> >
> >   This new callback would be called by the Monitor when the async
> > message API is called but we are in user mode.
> >
> >   This is really today's user_print, but user data is printed
> > asynchronously.
> >    
> 
> Even if we did that, it still suffers from the problem of a malicious or 
> broken guest that would not respond thereby hanging the monitor.

 True. We could print the timeout but that's not user friendly.

 Btw, I don't remember if I said that already but we could send
the command id with the timeout event.