Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753532AbZFSIQu (ORCPT ); Fri, 19 Jun 2009 04:16:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751880AbZFSIQf (ORCPT ); Fri, 19 Jun 2009 04:16:35 -0400 Received: from out01.mta.xmission.com ([166.70.13.231]:58385 "EHLO out01.mta.xmission.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750884AbZFSIQd (ORCPT ); Fri, 19 Jun 2009 04:16:33 -0400 To: "Jan Beulich" Cc: "Yinghai Lu" , "Jeremy Fitzhardinge" , "Len Brown" , "the arch\/x86 maintainers" , "Thomas Gleixner" , "Xen-devel" , "Ingo Molnar" , "Linux Kernel Mailing List" , "H. Peter Anvin" References: <4A329CF8.4050502@goop.org> <4A3A9220.4070807@goop.org> <4A3A99FB.7070807@goop.org> <4A3AC0C4.6060508@goop.org> <86802c440906182232r31088e4fh3613a8da6f8903f7@mail.gmail.com> <4A3B5FCD0200007800006AC0@vpn.id2.novell.com> From: ebiederm@xmission.com (Eric W. Biederman) Date: Fri, 19 Jun 2009 01:16:29 -0700 In-Reply-To: <4A3B5FCD0200007800006AC0@vpn.id2.novell.com> (Jan Beulich's message of "Fri\, 19 Jun 2009 08\:52\:13 +0100") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-XM-SPF: eid=;;;mid=;;;hst=in02.mta.xmission.com;;;ip=76.21.114.89;;;frm=ebiederm@xmission.com;;;spf=neutral X-SA-Exim-Connect-IP: 76.21.114.89 X-SA-Exim-Rcpt-To: JBeulich@novell.com, hpa@zytor.com, linux-kernel@vger.kernel.org, mingo@redhat.com, xen-devel@lists.xensource.com, tglx@linutronix.de, x86@kernel.org, lenb@kernel.org, jeremy@goop.org, yhlu.kernel@gmail.com X-SA-Exim-Mail-From: ebiederm@xmission.com X-Spam-DCC: XMission; sa02 1397; Body=1 Fuz1=1 Fuz2=1 X-Spam-Combo: ;"Jan Beulich" X-Spam-Relay-Country: X-Spam-Report: * -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP * 0.0 T_TM2_M_HEADER_IN_MSG BODY: T_TM2_M_HEADER_IN_MSG * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] * -0.0 DCC_CHECK_NEGATIVE Not listed in DCC * [sa02 1397; Body=1 Fuz1=1 Fuz2=1] * 0.0 T_TooManySym_01 4+ unique symbols in subject * 0.0 XM_SPF_Neutral SPF-Neutral * 0.0 T_TooManySym_02 5+ unique symbols in subject * 0.4 UNTRUSTED_Relay Comes from a non-trusted relay Subject: Re: [Xen-devel] Re: [PATCH RFC] x86/acpi: don't ignore I/O APICs justbecause there's no local APIC X-SA-Exim-Version: 4.2.1 (built Thu, 25 Oct 2007 00:26:12 +0000) X-SA-Exim-Scanned: Yes (on in02.mta.xmission.com) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1871 Lines: 45 "Jan Beulich" writes: >>>> Yinghai Lu 19.06.09 07:32 >>> >>doesn't XEN support per cpu irq vector? > > No. > >>got sth from XEN 3.3 / SLES 11 >> >>igb 0000:81:00.0: PCI INT A -> GSI 95 (level, low) -> IRQ 95 >>igb 0000:81:00.0: setting latency timer to 64 >>igb 0000:81:00.0: Intel(R) Gigabit Ethernet Network Connection >>igb 0000:81:00.0: eth9: (PCIe:2.5Gb/s:Width x4) 00:21:28:3a:d8:0e >>igb 0000:81:00.0: eth9: PBA No: ffffff-0ff >>igb 0000:81:00.0: Using MSI-X interrupts. 4 rx queue(s), 4 tx queue(s) >>vendor=8086 device=3420 >>(XEN) irq.c:847: dom0: invalid pirq 94 or vector -28 >>igb 0000:81:00.1: PCI INT B -> GSI 94 (level, low) -> IRQ 94 >>igb 0000:81:00.1: setting latency timer to 64 >>(XEN) physdev.c:87: dom0: map irq with wrong vector -28 >>map irq failed >>(XEN) physdev.c:87: dom0: map irq with wrong vector -28 >>map irq failed >> >>the system need a lot of MSI-X normally.. with current mainline tree >>kernel, it will need about 360 irq... > > Do you mean 360 connected devices, or just 360 IO-APIC pins (most of > which are usually unused)? In the latter case, devices using MSI (i.e. not > using high numbered IO-APIC pins) should work, while devices connected > to IO-APIC pins numbered 256 and higher won't work in SLE11 as-is. > This limitation got fixed recently in the 3.5-unstable tree, though. The > 256 active vectors limit, however, continues to exist, so the former case > would still not be supported by Xen. Good question. I know YH had a system a few years ago that exceeded 256 vectors. But in this case it really could be either. Eric -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/