From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=58236 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Q7YUz-0005xb-Cm
	for qemu-devel@nongnu.org; Wed, 06 Apr 2011 15:34:42 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1Q7YUx-0002Yg-7K
	for qemu-devel@nongnu.org; Wed, 06 Apr 2011 15:34:41 -0400
Received: from mail-gy0-f173.google.com ([209.85.160.173]:38555)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1Q7YUx-0002YN-4p
	for qemu-devel@nongnu.org; Wed, 06 Apr 2011 15:34:39 -0400
Received: by gyg4 with SMTP id 4so863865gyg.4
	for <qemu-devel@nongnu.org>; Wed, 06 Apr 2011 12:34:38 -0700 (PDT)
Message-ID: <4D9CC044.2000705@codemonkey.ws>
Date: Wed, 06 Apr 2011 14:34:28 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH 2/2 V7] qemu,qmp: add inject-nmi qmp command
References: <4D74A8C9.2020408@cn.fujitsu.com>
	<4D74A974.6090509@cn.fujitsu.com>	<20110404105949.GA30324@redhat.com>
	<4D99BF99.1040305@redhat.com>	<4D99C22C.4070401@codemonkey.ws>
	<20110406144723.45333682@doriath>	<4D9CAAF9.7000509@codemonkey.ws>
	<20110406150818.56707b9b@doriath>	<4D9CAE4B.7080305@siemens.com>
	<20110406160020.373cb5a2@doriath>
	<BANLkTinUfnq6b2u_bfdB_zc3z8dg=4gAbA@mail.gmail.com>
In-Reply-To: <BANLkTinUfnq6b2u_bfdB_zc3z8dg=4gAbA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
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.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: Peter Maydell <peter.maydell@linaro.org>
Cc: Lai Jiangshan <eag0628@gmail.com>, Jiangshan <laijs@cn.fujitsu.com>, kvm@vger.kernel.org, qemu-devel@nongnu.org, Jan Kiszka <jan.kiszka@siemens.com>, Markus Armbruster <armbru@redhat.com>, Luiz Capitulino <lcapitulino@redhat.com>, Avi Kivity <avi@redhat.com>

On 04/06/2011 02:27 PM, Peter Maydell wrote:
>> Right, but honestly speaking, I don't know how this works for other arches.
>>
>> So, the best thing to do is to have a general design that can be used
>> by any architecture. Of course that we can also add a new command later
>> if needed.
> Well, I'm not sure "send a random interrupt to the core" makes
> much sense for ARM... So what are we actually trying to model here?
> Some sort of way to do "press a front panel switch" via remote monitor
> protocol? I guess you could have an API for boards to register any
> switches they had...

http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=/liaai/crashdump/liaaicrashdumpnmiipmi.htm

If an OS is totally hosed (spinning with interrupts disabled), and NMI 
can be used to generate a crash dump.

It's a debug feature and modelling it exactly the way we are probably 
makes sense for other architectures too.  The real semantics are 
basically force guest crash dump.

Regards,

Anthony Liguori

> -- PMM
>