From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=41100 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PTBY0-00030l-Aq
	for qemu-devel@nongnu.org; Thu, 16 Dec 2010 05:59:01 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1PTBQe-0004Ug-Cl
	for qemu-devel@nongnu.org; Thu, 16 Dec 2010 05:51:21 -0500
Received: from mx1.redhat.com ([209.132.183.28]:61441)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1PTBQe-0004UZ-5a
	for qemu-devel@nongnu.org; Thu, 16 Dec 2010 05:51:20 -0500
Message-ID: <4D09EF22.4030706@redhat.com>
Date: Thu, 16 Dec 2010 12:51:14 +0200
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
References: <4D088F27.8000909@cn.fujitsu.com>	<20101215150911.14e1693f@doriath>	<4D08F868.5090100@redhat.com>	<20101215152606.078147ad@doriath>	<m3aak7ylp6.fsf@blackfin.pond.sub.org>	<20101215160000.16f85795@doriath>	<4D09D5EA.7070000@redhat.com>
	<20101216084815.3ca77188@doriath>
In-Reply-To: <20101216084815.3ca77188@doriath>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: [PATCH v3] qemu,
	qmp: convert do_inject_nmi() to QObject, QError
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.nongnu.org/archive/html/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: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel@nongnu.org, aliguori@us.ibm.com, Markus Armbruster <armbru@redhat.com>, kvm@vger.kernel.org, Lai Jiangshan <laijs@cn.fujitsu.com>

On 12/16/2010 12:48 PM, Luiz Capitulino wrote:
> Ok, I didn't know that, but I had another idea: the command could accept
> either a single cpu index or a list:
>
>
>    { "execute": "inject-nmi", "arguments": { "cpus": 2 } }
>
>    { "execute": "inject-nmi", "arguments": { "cpus": [1, 2, 3, 4] } }
>
> This has the feature of injecting the nmi in just some cpus, although I'm
> not sure this is going to be desired/useful.
>
> If we agree on this we'll have to wait because the monitor doesn't currently
> support "hybrid" arguments.

I hope it never does.  They're hard to support in old-school statically 
typed languages.

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