kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: Avi Kivity <avi@redhat.com>, kvm@vger.kernel.org
Subject: Re: nmi is broken?
Date: Sun, 24 Apr 2011 11:46:42 +0200	[thread overview]
Message-ID: <4DB3F182.3070006@web.de> (raw)
In-Reply-To: <87zkngypn8.fsf@devron.myhome.or.jp>

[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]

On 2011-04-24 11:17, OGAWA Hirofumi wrote:
> Avi Kivity <avi@redhat.com> writes:
> 
>>> With some debug, the cause seems to be in pit_do_work(). With the
>>> following patch, NMI watchdog seems to be working correctly (if irq
>>> disabled for long time, NMI watchdog can detect it).
>>>
>>> Is the following patch right?
>>
>> This would cause IRQs to be delivered even if the PIT is masked, no?
> 
> In here, mask means pit_mask_notifer()? If masked, ->pending doesn't
> prevent to fire it? I'm not sure.
> 
>> Are you in fact using the PIT?  Linux prefers the HPET, and in my 
>> experience the -no-hpet option makes NMIs work.
> 
> Yes, this is old kernel (2.6.9), and is not using HPET
> (CONFIG_HPET_TIMER=n), using IO-APIC as NMI source (PMU seems to be
> unsupported on kvm for now).
> 
> Unfortunately, -no-hpet didn't change situation. irq_stat.apic_timer_irqs
> and nmi_count() are same while irq is disabled.

Maybe it's a regression of latest NMI injection patches.

This worked before? Can you check if commits
c2dd554dc61173ecb6b3741b680d2ae4c245d2ba and
f86368493ec038218e8663cc1b6e5393cd8e008a have any impact on your problem?

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

  reply	other threads:[~2011-04-24  9:46 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21 19:21 nmi is broken? OGAWA Hirofumi
2011-04-23 22:50 ` OGAWA Hirofumi
2011-04-24  6:44   ` Avi Kivity
2011-04-24  9:17     ` OGAWA Hirofumi
2011-04-24  9:46       ` Jan Kiszka [this message]
2011-04-24 11:13         ` OGAWA Hirofumi
2011-04-24 11:15           ` OGAWA Hirofumi
2011-04-24 12:24     ` Jan Kiszka
2011-04-27  8:55       ` Avi Kivity
2011-04-27 12:09         ` Jan Kiszka
2011-04-28  1:28         ` OGAWA Hirofumi
2011-04-28  9:59           ` Avi Kivity
2011-04-28 13:44             ` OGAWA Hirofumi
2011-04-28 14:23               ` OGAWA Hirofumi
2011-05-01  1:45                 ` OGAWA Hirofumi
2011-05-02  8:46                   ` Avi Kivity
2011-05-02 14:30                     ` OGAWA Hirofumi
2011-05-03  9:36                       ` Avi Kivity
2011-05-03 10:07                         ` Avi Kivity
2011-05-03 13:25                           ` OGAWA Hirofumi
2011-05-03 13:35                             ` Avi Kivity
2011-05-03 16:57                               ` OGAWA Hirofumi
2011-05-03 17:09                                 ` Avi Kivity
2011-05-03 17:45                                   ` OGAWA Hirofumi
2011-05-04  8:27                                     ` Avi Kivity
2011-05-04 15:40                                       ` OGAWA Hirofumi
2011-05-04 16:15                                         ` Avi Kivity
2011-04-24 14:08     ` Jan Kiszka
2011-05-03  9:43       ` Avi Kivity
2011-05-03 10:37         ` Jan Kiszka
2011-05-03 13:31           ` Avi Kivity
2011-05-03 14:29             ` Jan Kiszka
2011-05-03 14:37               ` Avi Kivity
2011-05-03 15:01                 ` 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=4DB3F182.3070006@web.de \
    --to=jan.kiszka@web.de \
    --cc=avi@redhat.com \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=kvm@vger.kernel.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).