From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Yang, Sheng" <sheng.yang@intel.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: Re: [RFC][PATCH 0/4] Enabled NMI support for KVM
Date: Thu, 08 May 2008 13:31:29 +0200 [thread overview]
Message-ID: <4822E491.3010605@siemens.com> (raw)
In-Reply-To: <200805081655.32262.sheng.yang@intel.com>
Yang, Sheng wrote:
> Hi
>
> This patchset enabled NMI support for KVM.
>
> The first three patches enabled NMI for in-kernel irqchip and NMI supporting
> on VMX. The last patch enabled NMI watchdog in linux, can be used to test the
> NMI injection.
>
> In fact, this series should also included Jan Kiszka's patch to enable NMI for
> userspace irqchip, but now I got little trouble to get the merged version
> work on my machine... We would post it as soon as we solved it.
>
> Another thing is the vmx_intr_assist() and do_interrupt_requests() got some
> duplication. And the logic for normal interrupt and NMI is similiar, but
> vmx_intr_assist() seems a little implicit...
>
> Any comments welcome!
To make rebasing my work easier (hope I find some time later today):
Your patches show up line-wrapped here. Could you check and repost?
Thanks,
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
next prev parent reply other threads:[~2008-05-08 11:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 8:55 [RFC][PATCH 0/4] Enabled NMI support for KVM Yang, Sheng
2008-05-08 11:31 ` Jan Kiszka [this message]
2008-05-08 15:57 ` 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=4822E491.3010605@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=sheng.yang@intel.com \
/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