Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756252AbYKQCDT (ORCPT ); Sun, 16 Nov 2008 21:03:19 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754657AbYKQCDJ (ORCPT ); Sun, 16 Nov 2008 21:03:09 -0500 Received: from relay1.sgi.com ([192.48.179.29]:44683 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754654AbYKQCDI (ORCPT ); Sun, 16 Nov 2008 21:03:08 -0500 Message-ID: <4920D0D7.7050905@sgi.com> Date: Sun, 16 Nov 2008 18:03:03 -0800 From: Mike Travis User-Agent: Thunderbird 2.0.0.6 (X11/20070801) MIME-Version: 1.0 To: "H. Peter Anvin" CC: Yinghai Lu , Benjamin Herrenschmidt , Andrew Morton , mingo@elte.hu, tglx@linutronix.de, linux-kernel@vger.kernel.org Subject: Re: [PATCH] sparse_irq aka dyn_irq v13 References: <491434FB.2050904@kernel.org> <20081107124957.GA21709@elte.hu> <49168BD3.5010204@kernel.org> <20081109073813.GA17180@elte.hu> <86802c440811090003g5ac53822y852a4c1096228f8b@mail.gmail.com> <20081110094033.GL22392@elte.hu> <20081110015511.453a801e.akpm@linux-foundation.org> <4918065A.6050402@kernel.org> <20081110100329.GA19970@elte.hu> <491A9F87.8040403@kernel.org> <20081112120814.GG11352@elte.hu> <491C8B38.9060901@kernel.org> <20081113131850.d94fb229.akpm@linux-foundation.org> <1226869137.7178.175.camel@pasglop> <4920B069.5020203@kernel.org> <4920B15E.6090200@zytor.com> <4920B2A4.4040900@kernel.org> <4920B3E3.4050707@zytor.com> <4920B911.7060504@kernel.org> <4920BA3A.5090100@zytor.com> <4920BCA8.6080600@kernel.org> <4920BF62.10700@zytor.com> <4920C19E.8090402@kernel.org> <4920C21C.2030605@zytor.com> In-Reply-To: <4920C21C.2030605@zytor.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 784 Lines: 24 H. Peter Anvin wrote: > Yinghai Lu wrote: >> so we have one list to map domain/bus/dev/func to bits [31,12] in irq ? >> > > That works, although having a more generic allocation mechanism which > isn't so tied to MSI-X would make more sense. > > -hpa Hmm, I see I picked up this conversation quite late. I would agree that trying to map any set of fixed bit fields to domain/bus/device/function would be problematic (esp. since I don't understand how MSI's figure into the deal.) Is there some reason why we need that? Thanks, Mike -- 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/