public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Yang, Sheng" <sheng.yang@intel.com>
Cc: kvm-devel <kvm@vger.kernel.org>, Avi Kivity <avi@qumranet.com>
Subject: Re: [PATCH 5/9] kvm-x86: Enable NMI Watchdog via in-kernel PIT source
Date: Tue, 23 Sep 2008 17:04:48 +0200	[thread overview]
Message-ID: <48D90590.6050705@siemens.com> (raw)
In-Reply-To: <200809231410.33041.sheng.yang@intel.com>

Yang, Sheng wrote:
> On Friday 19 September 2008 20:03:02 Jan Kiszka wrote:
>> LINT0 of the LAPIC can be used to route PIT events as NMI watchdog
>> ticks into the guest. This patch aligns the in-kernel irqchip emulation
>> with the user space irqchip with already supports this feature. The
>> trick is to route PIT interrupts to all LAPIC's LVT0 lines.
>>
>> Rebased patch and slightly polished patch originally posted by Sheng
>> Yang.
> 
> Signed-off-by: Sheng Yang <sheng.yang@intel.com>
> 
> Thanks for pick up this patch again! 
> 
> Have you test some Windows guest with this watchdog? Last time I dropped it 
> because it cause BSOD on some version of Windows(IRQ_NOT_EQUAL_OR_LESS). I 
> don't remember the exactly situation there, but you may have a try. 

Not yet. I always tell my colleagues that I don't need Windows on my
desktop, I just need a few VM images - for testing... :)

I will try to dig out / generate some image and reproduce the issue you
and Gleb see. Hope it will trigger here as well. Anything special
required to make Windows use the NMI as watchdog?

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux

  reply	other threads:[~2008-09-23 15:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-19 12:06 [PATCH 0/9] Enhance NMI support of KVM - v2 Jan Kiszka
2008-09-19 11:59 ` [PATCH 1/9] VMX: include all IRQ window exits in statistics Jan Kiszka
2008-09-19 12:01 ` [PATCH 2/9] VMX: refactor/fix IRQ and NMI injectability determination Jan Kiszka
2008-09-19 12:01 ` [PATCH 3/9] VMX: refactor IRQ and NMI window enabling Jan Kiszka
2008-09-19 12:02 ` [PATCH 4/9] VMX: fix real-mode NMI support Jan Kiszka
2008-09-19 12:03 ` [PATCH 5/9] kvm-x86: Enable NMI Watchdog via in-kernel PIT source Jan Kiszka
2008-09-19 16:55   ` Jan Kiszka
2008-09-23  6:10   ` Yang, Sheng
2008-09-23 15:04     ` Jan Kiszka [this message]
2008-09-24 10:18       ` Yang, Sheng
2008-09-19 12:03 ` [PATCH 6/9] kvm-x86: Support for user space injected NMIs Jan Kiszka
2008-09-19 12:03 ` [PATCH 7/9] VMX: Provide support " Jan Kiszka
2008-09-19 12:04 ` [PATCH 8/9] VMX: work around lacking VNMI support Jan Kiszka
2008-09-21 14:31   ` Gleb Natapov
2008-09-21 16:57     ` Jan Kiszka
2008-09-21 18:08       ` Jan Kiszka
2008-09-22  6:41       ` Gleb Natapov
2008-09-22  7:19         ` Jan Kiszka
2008-09-22  7:39           ` Gleb Natapov
2008-09-22  7:48             ` Jan Kiszka
2008-09-19 12:05 ` [PATCH 9/9] kvm: Enable NMI support for userspace irqchip Jan Kiszka
2008-09-19 12:10 ` [PATCH 0/9] Enhance NMI support of KVM - v2 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=48D90590.6050705@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=avi@qumranet.com \
    --cc=kvm@vger.kernel.org \
    --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