From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: [patch 00/47] Sparse irq rework Date: Mon, 11 Oct 2010 22:34:46 +1100 Message-ID: <1286796886.5220.4.camel@pasglop> References: <20100930221351.682772535@linutronix.de> <20101003112312.GB9844@angua.secretlab.ca> <20101003112920.GB32736@n2100.arm.linux.org.uk> <4CACFC23.4080504@kernel.org> <4CAD082B.40908@kernel.org> <4CAD1154.3080403@kernel.org> <4CAD4EC3.5060809@kernel.org> <4CAFEEFA.1070000@kernel.org> <4CB00122.3030301@kernel.org> <4CB014F5.5080209@kernel.org> <4CB28988.4090207@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: Received: from gate.crashing.org ([63.228.1.57]:46616 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753072Ab0JKLfh (ORCPT ); Mon, 11 Oct 2010 07:35:37 -0400 In-Reply-To: Sender: linux-arch-owner@vger.kernel.org List-ID: To: Thomas Gleixner Cc: Yinghai Lu , Grant Likely , Russell King - ARM Linux , LKML , linux-arch@vger.kernel.org, Linus Torvalds , Andrew Morton , x86@kernel.org, Peter Zijlstra , Paul Mundt , David Woodhouse , Jesse Barnes , "Eric W. Biederman" , Suresh Siddha > Hmm, that's probably a problem for all legacy interrupts which are > never torn down once they are set up. And we set them all up during > early boot. > > So either we special case the legacy area or remove the warning > alltogether. > > Another option I discussed with Suresh recently is to remove the > allocator in intr_remapping.c and just embedd irq_2_iommu into > irq_cfg. Just in case that's of use, on powerpc, we just special case the legacy range. It's keep un-requestable unless somebody comes and explicitely claims it (using a special flag for our virq scheme, typically only 8259 does it for us) and then we get 1:1 all pre-allocated and mostly immutable. Cheers, Ben.