From: "Yang, Sheng" <sheng.yang@intel.com>
To: " kvm-devel" <kvm-devel@lists.sourceforge.net>
Subject: [PATCH 0/2] NMI supporting for KVM and VMX v2
Date: Thu, 15 May 2008 18:50:25 +0800 [thread overview]
Message-ID: <200805151850.25870.sheng.yang@intel.com> (raw)
Hi
Sorry for the update delays, got a cold recently...
No big modification. I dropped the ordinary first patch following Avi's
comment, and fixed a bug when handling host NMI in vmx_vcpu_run in second
patch.
The third patch of enabling NMI watchdog is *not* meant to be merged. It was
cooked for the test, and it would bring some overhead on interrupt handling,
as well as regression on some version of Windows now(IRQ_NOT_EQUAL_OR_LESS
BSOD). But is it necessary to got NMI watchdog support in KVM? If so, maybe
we need a option(or kernel module parameter) to enable it.
--
Thanks
Yang, Sheng
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
reply other threads:[~2008-05-15 10:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200805151850.25870.sheng.yang@intel.com \
--to=sheng.yang@intel.com \
--cc=kvm-devel@lists.sourceforge.net \
/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