From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NGLUr-0002qp-VX
	for qemu-devel@nongnu.org; Thu, 03 Dec 2009 18:54:06 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NGLUn-0002id-2u
	for qemu-devel@nongnu.org; Thu, 03 Dec 2009 18:54:05 -0500
Received: from [199.232.76.173] (port=50712 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NGLUm-0002ia-UW
	for qemu-devel@nongnu.org; Thu, 03 Dec 2009 18:54:00 -0500
Received: from mx1.redhat.com ([209.132.183.28]:42548)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <lcapitulino@redhat.com>) id 1NGLUm-0002CT-JJ
	for qemu-devel@nongnu.org; Thu, 03 Dec 2009 18:54:00 -0500
Date: Thu, 3 Dec 2009 21:53:50 -0200
From: Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] Staging update (0.12 pending freeze)
Message-ID: <20091203215350.7159df5d@doriath>
In-Reply-To: <4B1847EE.7060706@codemonkey.ws>
References: <4B1699D3.8010908@codemonkey.ws> <4B17B057.1070004@redhat.com>
	<4B1847EE.7060706@codemonkey.ws>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Gerd Hoffmann <kraxel@redhat.com>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>

On Thu, 03 Dec 2009 17:21:18 -0600
Anthony Liguori <anthony@codemonkey.ws> wrote:

> > Finally the 'default devices' patch series ('must have' IMHO):
> >
> >   http://patchwork.ozlabs.org/patch/39180/ (patch 1/10)
> >
> > Without that one using -device and -readconfig becomes much harder.
> 
> This series doesn't get along with the QMP monitor support that's been 
> added recently.  That's because there is now a set of monitor flags and 
> -monitor takes more than a character device as an argument.

 For QMP there is only one flag, which is 'control', like:

-monitor control,<device>

 Multiple Monitors work just fine, like:

-monitor stdio -monitor control,tcp:localhost:444,server

 I've even tested multiple QMP monitors iirc. :)

> Honestly, I don't really like multiplexing the -monitor option to 
> support qmp.  I think I would have a proper -qmp option at the top 
> level.  That would integrate much more nicely too with this default 
> devices series.  Luiz, what do you think?

 Multiplexing the monitor is really useful for testing and it doesn't
seem reasonable to me to drop this feature just because we can't
add a single flag to an existing command-line option.