From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Gleixner Subject: Re: [Patch V3 19/37] x86, irq: introduce mechanisms to support dynamically allocate IRQ for IOAPIC Date: Wed, 28 May 2014 23:22:06 +0200 (CEST) Message-ID: References: <1401178092-1228-1-git-send-email-jiang.liu@linux.intel.com> <1401178092-1228-20-git-send-email-jiang.liu@linux.intel.com> <53856D8E.3010401@linux.intel.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: In-Reply-To: Sender: linux-pci-owner@vger.kernel.org To: Jiang Liu Cc: Benjamin Herrenschmidt , Grant Likely , Ingo Molnar , "H. Peter Anvin" , "Rafael J. Wysocki" , Bjorn Helgaas , Randy Dunlap , Yinghai Lu , x86@kernel.org, Len Brown , Pavel Machek , Konrad Rzeszutek Wilk , Andrew Morton , Tony Luck , Joerg Roedel , Paul Gortmaker , Greg Kroah-Hartman , linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org, Ingo Molnar , linux-pm@vger.kernel.org List-Id: linux-pm@vger.kernel.org On Wed, 28 May 2014, Thomas Gleixner wrote: > On Wed, 28 May 2014, Jiang Liu wrote: > > This is used to work around special non-ISA interrupts with GSI below > > NR_IRQS_LEGACY. The original code for the special case is: > > /* > > * Provide an identity mapping of gsi == irq except on truly > > * weird platforms that have non isa irqs in the first 16 gsis. > > */ > > return gsi >= NR_IRQS_LEGACY ? gsi : gsi_top + gsi; > > That looks really, really wrong. What's wrong with assigning that irq > irq number on those platforms? > > The weird stuff is SFI and devicetree, if I understand your code > correctly. > > So if those platforms do not have actual legacy irqs, what's wrong > with giving out the legacy numbers? Though if it's a real issue, we can simply mark the ioapic on those devices as DYNAMIC and avoid that whole magic. Thanks, tglx