All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: Jan Kiszka <jan.kiszka@web.de>, kvm@vger.kernel.org
Subject: Re: nmi is broken?
Date: Wed, 04 May 2011 11:27:55 +0300	[thread overview]
Message-ID: <4DC10E0B.3000605@redhat.com> (raw)
In-Reply-To: <877ha7lluc.fsf@devron.myhome.or.jp>

On 05/03/2011 08:45 PM, OGAWA Hirofumi wrote:
> Avi Kivity<avi@redhat.com>  writes:
>
> >  On 05/03/2011 07:57 PM, OGAWA Hirofumi wrote:
> >>  >
> >>  >   Usually yes, but we already have the PIT wired to INTIN0.  I saw that
> >>  >   the kernel consults the mptable to see which pin to use, so with the
> >>  >   right BIOS magic we can get things to work.
> >>
> >>  Um..., I'm confused more. If so, MADT doesn't say it. MADT says irq == 0
> >>  is pin == 2, this is one of reasons why linux is quite silent in
> >>  check_timer(). And I can't see why it is working by pin == 2 for IOAPIC.
> >>
> >>  If I can make time, I'll see what happens by pin == 2 and pin == 0 of
> >>  IOAPIC in kvm.
> >
> >  You're right.  The default routing is INTIN0, but qemu changes it to
> >  INTIN2 and tells kvm.
> >
> >  So INTIN0 is free for the 8259A output.
>
> I see. Did it mean qemu changes the wiring, so kvm can't work for live
> migration with it?

qemu changes the wiring, but it does so on both the migration source and 
the migration target (before either is launched), so they are migration 
compatible.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2011-05-04  8:28 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
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 [this message]
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=4DC10E0B.3000605@redhat.com \
    --to=avi@redhat.com \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=jan.kiszka@web.de \
    --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.