From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastian Blank Subject: Re: pvops-2.6.32 - Interrupt routing problem Date: Mon, 15 Mar 2010 11:36:22 +0100 Message-ID: <20100315103622.GA25174@wavehammer.waldi.eu.org> References: <20100310111923.GA7087@wavehammer.waldi.eu.org> <20100314140813.GA5309@wavehammer.waldi.eu.org> <20100314152334.GA6483@wavehammer.waldi.eu.org> <4B9D0726.3060304@goop.org> <20100314161750.GA7790@wavehammer.waldi.eu.org> <20100315101126.GA24650@wavehammer.waldi.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Content-Disposition: inline In-Reply-To: <20100315101126.GA24650@wavehammer.waldi.eu.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Zhang, Xiantao" Cc: Jeremy Fitzhardinge , "xen-devel@lists.xensource.com" , Keir Fraser List-Id: xen-devel@lists.xenproject.org On Mon, Mar 15, 2010 at 11:11:26AM +0100, Bastian Blank wrote: > On Mon, Mar 15, 2010 at 12:30:32PM +0800, Zhang, Xiantao wrote: > > Could you try the following patch ? Currently, the GSI 0-15 's polarity and trigger mode are determined by hypervisor, and maybe hypervisor and dom0 has no agreement to determin them. Just follow dom0's setting with this patch, and I think it maybe work for you. > No, it does not. mp_register_gsi also disallows reprogramming of already > setup IO-APIC entries. But if I force it with the following hack, it > works. So I would assume this a bug in the hypervisor to setup the GSI > without knowing anything about it. Or are they pre-programmed by the BIOS? IO-APIC info from Xen now: (XEN) IO APIC #8...... (XEN) .... register #00: 08000000 (XEN) ....... : physical APIC id: 08 (XEN) ....... : Delivery Type: 0 (XEN) ....... : LTS : 0 (XEN) .... register #01: 000F0011 (XEN) ....... : max redirection entries: 000F (XEN) ....... : PRQ implemented: 0 (XEN) ....... : IO APIC version: 0011 (XEN) .... register #02: 08000000 (XEN) ....... : arbitration: 08 (XEN) .... IRQ redirection table: (XEN) NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: (XEN) 00 000 00 1 0 0 0 0 0 0 00 (XEN) 01 000 00 0 0 0 0 0 0 0 28 (XEN) 02 000 00 0 0 0 0 0 0 0 F0 (XEN) 03 000 00 0 0 0 0 0 0 0 30 (XEN) 04 000 00 0 0 0 0 0 0 0 F1 (XEN) 05 000 00 1 0 0 0 0 0 0 38 (XEN) 06 000 00 1 0 0 0 0 0 0 40 (XEN) 07 000 00 1 0 0 0 0 0 0 48 (XEN) 08 000 00 0 0 0 0 0 0 0 50 (XEN) 09 000 00 0 0 0 0 0 0 0 58 (XEN) 0a 000 00 1 0 0 0 0 0 0 60 (XEN) 0b 000 00 1 0 0 0 0 0 0 68 (XEN) 0c 000 00 0 0 0 0 0 0 0 70 (XEN) 0d 000 00 1 0 0 0 0 0 0 78 (XEN) 0e 00A 0A 0 1 0 1 0 0 0 9A (XEN) 0f 000 00 1 0 0 0 0 0 0 90 If I read the code correctly, the 1 in the trigger line means level triggered. But the Linux kernel still lists it as edge triggered. Bastian -- "We have the right to survive!" "Not by killing others." -- Deela and Kirk, "Wink of An Eye", stardate 5710.5