From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=44061 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Q7u0m-0006oK-Ni
	for qemu-devel@nongnu.org; Thu, 07 Apr 2011 14:32:57 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1Q7u0l-0007sG-HZ
	for qemu-devel@nongnu.org; Thu, 07 Apr 2011 14:32:56 -0400
Received: from mail-yw0-f45.google.com ([209.85.213.45]:38112)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1Q7u0l-0007sA-Cx
	for qemu-devel@nongnu.org; Thu, 07 Apr 2011 14:32:55 -0400
Received: by ywl41 with SMTP id 41so1394438ywl.4
	for <qemu-devel@nongnu.org>; Thu, 07 Apr 2011 11:32:54 -0700 (PDT)
Message-ID: <4D9E0352.2050204@codemonkey.ws>
Date: Thu, 07 Apr 2011 13:32:50 -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>	<4D9CC044.2000705@codemonkey.ws>
	<BANLkTim4iP_YRjOCYH986BB=ec-dwcjfQA@mail.gmail.com>
In-Reply-To: <BANLkTim4iP_YRjOCYH986BB=ec-dwcjfQA@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, Jan Kiszka <jan.kiszka@siemens.com>, Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>, Luiz Capitulino <lcapitulino@redhat.com>

On 04/07/2011 01:10 PM, Peter Maydell wrote:
> On 6 April 2011 20:34, Anthony Liguori<anthony@codemonkey.ws>  wrote:
>> 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.
> Ah, right. (There isn't really an equivalent to this on ARM since
> we don't have a real NMI equivalent. So any implementation for ARM
> qemu would be board dependent since you could wire a watchdog up to
> any interrupt.)
>
> Should we try to pick a command name that says what it's supposed to
> do rather than how it happens to be implemented on x86 ?

Yup, I was thinking the same thing after I sent the note above.  If we 
call it 'force-crash-dump', we can implement it as an NMI on target-i386 
and potentially as something else on a different target.

Regards,

Anthony Liguori

> -- PMM
>