From: Jeremy Fitzhardinge Subject: Re: [PATCH 1/5] xen: events: use irq_alloc_desc(_at) instead of open-coding an IRQ allocator. Date: Mon, 25 Oct 2010 16:21:43 -0700 Message-ID: <4CC61107.4070200@goop.org> References: <1288023736.11153.40.camel@zakaz.uk.xensource.com> <1288023813-31989-1-git-send-email-ian.campbell@citrix.com> <20101025173522.GA5590@dumpdata.com> <4CC60CB7.3070005@goop.org> <4CC60D3A.1020201@zytor.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4CC60D3A.1020201@zytor.com> Sender: linux-kernel-owner@vger.kernel.org To: "H. Peter Anvin" Cc: Konrad Rzeszutek Wilk , Ian Campbell , Stefano Stabellini , linux-kernel@vger.kernel.org, mingo@elte.hu, xen-devel@lists.xensource.com, tglx@linutronix.de List-Id: xen-devel@lists.xenproject.org On 10/25/2010 04:05 PM, H. Peter Anvin wrote: > On 10/25/2010 04:03 PM, Jeremy Fitzhardinge wrote: >> What? Why? How? Surely if we're asking the irq subsystem to allocate >> us an irq, it will return a fresh never-before-used (and certainly not >> shared) irq? Shared irqs only make sense if multiple devices are >> actually sharing, say, a wire on the board. >> >> Or am I missing something? >> > I think the number is not necessarily "never before used", but rather > "not currently used". Yeah, that's what I meant. J