All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel@nongnu.org, aliguori@us.ibm.com,
	Avi Kivity <avi@redhat.com>,
	Markus Armbruster <armbru@redhat.com>
Subject: [Qemu-devel] Re: ANN: QEMU Monitor Protocol git tree
Date: Wed, 11 Nov 2009 11:59:01 +0200	[thread overview]
Message-ID: <20091111095901.GA3387@redhat.com> (raw)
In-Reply-To: <20090924101458.00d65388@doriath>

On Thu, Sep 24, 2009 at 10:14:58AM -0300, Luiz Capitulino wrote:
> On Thu, 24 Sep 2009 16:07:28 +0300
> Avi Kivity <avi@redhat.com> wrote:
> 
> > On 09/24/2009 04:05 PM, Luiz Capitulino wrote:
> > >>>    I think the easiest way to have this would be to add a
> > >>> monitor command to disable capabilities. Like a command to
> > >>> disable async messages.
> > >>>
> > >>>        
> > >> Other way around, enable things that you want.
> > >>      
> > >   Ok, I will add support for this in my tree then, async messages
> > > will be considered a capability.
> > >    
> > 
> > Actually, if async messages are specified from day one they can be 
> > always active.  The client can easily ignore them.
> 
>  That's also fine by me, but we were talking about having a
> command to disable async messages... If we do this, I would
> prefer to make it a capability instead, this way it can use
> the same infrastructure (as opposed to special treatment).

Maybe per message type (error/warning/info/debug).

-- 
MST

  reply	other threads:[~2009-11-11 10:01 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-22  1:44 [Qemu-devel] ANN: QEMU Monitor Protocol git tree Luiz Capitulino
2009-09-23  1:56 ` Anthony Liguori
2009-09-23  9:57   ` Daniel P. Berrange
2009-09-23 10:57     ` Avi Kivity
2009-09-23 13:40       ` [Qemu-devel] " Paolo Bonzini
2009-09-23 14:04         ` Avi Kivity
2009-09-23 15:19           ` Nathan Baum
2009-09-23 15:40             ` Luiz Capitulino
2009-09-23 18:15           ` Anthony Liguori
2009-09-23 18:36             ` Jamie Lokier
2009-09-23 18:45               ` Paolo Bonzini
2009-09-23 16:01     ` [Qemu-devel] " Markus Armbruster
2009-09-23 16:11       ` Luiz Capitulino
2009-09-23 18:15         ` Jamie Lokier
2009-09-23 18:18       ` Anthony Liguori
2009-09-23 17:08     ` Daniel P. Berrange
2009-09-23 19:07       ` Luiz Capitulino
2009-09-23 14:18   ` Luiz Capitulino
2009-09-23 18:21     ` Anthony Liguori
2009-09-23 10:08 ` Daniel P. Berrange
2009-09-23 14:21   ` Luiz Capitulino
2009-09-23 15:55   ` Markus Armbruster
2009-09-23 22:37 ` Markus Armbruster
2009-09-24 12:31   ` Luiz Capitulino
2009-09-24 12:44     ` Avi Kivity
2009-09-24 13:05       ` Luiz Capitulino
2009-09-24 13:07         ` Avi Kivity
2009-09-24 13:14           ` Luiz Capitulino
2009-11-11  9:59             ` Michael S. Tsirkin [this message]
2009-09-24 13:28     ` Markus Armbruster
2009-09-24 19:09       ` Luiz Capitulino
2009-11-11 10:03       ` [Qemu-devel] " Michael S. Tsirkin
2009-11-13  8:38         ` Markus Armbruster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091111095901.GA3387@redhat.com \
    --to=mst@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=armbru@redhat.com \
    --cc=avi@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.