From: Jan Kiszka <jan.kiszka@web.de>
To: Andi Kleen <andi@firstfloor.org>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 1/3] x86: Introduce CPU_INTERRUPT_NMI
Date: Mon, 14 Apr 2008 18:13:30 +0200 [thread overview]
Message-ID: <480382AA.8060004@web.de> (raw)
In-Reply-To: <87zlrwvj00.fsf@basil.nowhere.org>
[-- Attachment #1: Type: text/plain, Size: 870 bytes --]
Andi Kleen wrote:
> Jan Kiszka <jan.kiszka@web.de> writes:
>
>> [ 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.
>
> 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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]
next prev parent reply other threads:[~2008-04-14 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-12 16:12 [Qemu-devel] [PATCH 1/3] x86: Introduce CPU_INTERRUPT_NMI Jan Kiszka
2008-04-12 16:48 ` [Qemu-devel] " Jan Kiszka
2008-04-14 10:16 ` Andi Kleen
2008-04-14 16:13 ` Jan Kiszka [this message]
2008-04-14 16:17 ` Andi Kleen
2008-04-14 16:38 ` Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=480382AA.8060004@web.de \
--to=jan.kiszka@web.de \
--cc=andi@firstfloor.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).