From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JlRKb-0000yx-Vc for qemu-devel@nongnu.org; Mon, 14 Apr 2008 12:14:58 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JlRKS-0000tX-VQ for qemu-devel@nongnu.org; Mon, 14 Apr 2008 12:14:55 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JlRKS-0000sx-Nb for qemu-devel@nongnu.org; Mon, 14 Apr 2008 12:14:48 -0400 Received: from fmmailgate03.web.de ([217.72.192.234]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JlRKN-0002u9-Os for qemu-devel@nongnu.org; Mon, 14 Apr 2008 12:14:45 -0400 Message-ID: <480382AA.8060004@web.de> Date: Mon, 14 Apr 2008 18:13:30 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <4800DF6A.5010700@web.de> <87zlrwvj00.fsf@basil.nowhere.org> In-Reply-To: <87zlrwvj00.fsf@basil.nowhere.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig086FC144DD8394990919F360" Sender: jan.kiszka@web.de Subject: [Qemu-devel] Re: [PATCH 1/3] x86: Introduce CPU_INTERRUPT_NMI Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Andi Kleen Cc: qemu-devel@nongnu.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig086FC144DD8394990919F360 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Andi Kleen wrote: > Jan Kiszka writes: >=20 >> [ This patch obsoletes >> http://permalink.gmane.org/gmane.comp.emulators.qemu/22989. ] >> >> The x86 emulation yet lacks proper NMI support. This patch introduces >> CPU_INTERRUPT_NMI and the required handling logic so that hardware >> emulation drivers can simply call >> >> cpu_interrupt(env, CPU_INTERRUPT_NMI); >> >> to raise an NMI on this arch. >=20 > Could you please add a monitor command to raise it too? Some OS support= > triggering debugging code from NMIs and that might be useful > inside qemu too. Will it be enough just the raise the NMI? Or doesn't you also have to modify some hardware state somewhere? Maybe you could provide an example for what you have in mind (it's trivial to hack such an extension, I'm just curious to understand its background). Jan --------------enig086FC144DD8394990919F360 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFIA4KtniDOoMHTA+kRAgOOAJ0Q+KCM7BwN0ncW0BG/VcwnYpFIXgCggZRt kt0Y72GRq/o/c7NevF0tqM4= =y5MT -----END PGP SIGNATURE----- --------------enig086FC144DD8394990919F360--