From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: nmi is broken? Date: Tue, 03 May 2011 20:09:51 +0300 Message-ID: <4DC036DF.4010101@redhat.com> References: <87sjtbe7fz.fsf@devron.myhome.or.jp> <877hak1t1s.fsf@devron.myhome.or.jp> <4DB3C6D3.9040703@redhat.com> <4DB41696.6060606@web.de> <4DB7DA11.8040503@redhat.com> <871v0njhab.fsf@devron.myhome.or.jp> <4DB93A6D.3010703@redhat.com> <87sjt2ij8b.fsf@devron.myhome.or.jp> <87k4eeihdu.fsf@devron.myhome.or.jp> <87mxj7urb0.fsf@devron.myhome.or.jp> <4DBE6F6B.6090103@redhat.com> <8739kxgoo0.fsf@devron.myhome.or.jp> <4DBFCC81.9080401@redhat.com> <4DBFD3F5.8020406@redhat.com> <87hb9blxvt.fsf@devron.myhome.or.jp> <4DC004B6.3030503@redhat.com> <87bozjlo20.fsf@devron.myhome.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jan Kiszka , kvm@vger.kernel.org To: OGAWA Hirofumi Return-path: Received: from mx1.redhat.com ([209.132.183.28]:7973 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753988Ab1ECRJ4 (ORCPT ); Tue, 3 May 2011 13:09:56 -0400 In-Reply-To: <87bozjlo20.fsf@devron.myhome.or.jp> Sender: kvm-owner@vger.kernel.org List-ID: 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. -- error compiling committee.c: too many arguments to function