From: Avi Kivity <avi@redhat.com>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: kvm@vger.kernel.org
Subject: Re: nmi is broken?
Date: Sun, 24 Apr 2011 09:44:35 +0300 [thread overview]
Message-ID: <4DB3C6D3.9040703@redhat.com> (raw)
In-Reply-To: <877hak1t1s.fsf@devron.myhome.or.jp>
On 04/24/2011 01:50 AM, OGAWA Hirofumi wrote:
> OGAWA Hirofumi<hirofumi@mail.parknet.co.jp> writes:
>
> > I noticed recently NMI on guest kernel is not working well. host/guest
> > kernel is 2.6.39-rc4, and using vmx.
> >
> > And test code is something like the following:
> >
> > local_irq_disable();
> > for (i = 0; i< 10; i++) {
> > int cpu = get_cpu();
> > printk("%s: nmi %u, lapic %u\n", __FUNCTION__,
> > nmi_count(cpu), irq_stat[cpu].apic_timer_irqs);
> > mdelay(1000);
> > put_cpu();
> > }
> >
> > the result is both of nmi and lapic are not increased. If I used
> > -no-kvm-irqchip, it works fine (increase nmi only). So, it seems to be
> > the bug of kvm driver side.
>
> 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?
Are you in fact using the PIT? Linux prefers the HPET, and in my
experience the -no-hpet option makes NMIs work.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2011-04-24 6:44 UTC|newest]
Thread overview: 36+ 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 [this message]
2011-04-24 9:17 ` OGAWA Hirofumi
2011-04-24 9:46 ` Jan Kiszka
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
-- strict thread matches above, loose matches on Subject: below --
2001-11-30 9:10 NMI is broken! george anzinger
2001-12-01 7:11 ` george anzinger
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=4DB3C6D3.9040703@redhat.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.