From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [203.10.76.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.ozlabs.org", Issuer "CA Cert Signing Authority" (verified OK)) by bilbo.ozlabs.org (Postfix) with ESMTPS id 079EFB7089 for ; Thu, 16 Jul 2009 00:11:30 +1000 (EST) Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 4EC8DDDD1C for ; Thu, 16 Jul 2009 00:11:28 +1000 (EST) Message-Id: <761CE7B3-A7FD-41FD-A828-B9F17F73DF32@kernel.crashing.org> From: Kumar Gala To: Benjamin Herrenschmidt Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Mime-Version: 1.0 (Apple Message framework v935.3) Subject: having access to interrupt specifier in map() function Date: Wed, 15 Jul 2009 09:11:22 -0500 Cc: "linuxppc-dev@ozlabs.org list" List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Ben, Do you have any ideas on keeping access to the interrupt specifier around so when we call map() we have access to it. Our HV guys are looking at using additional bits in the interrupt specifier to encode information beyond just level/sense of the IRQ and want to make decisions based on it during map(). Maybe we can keep it around in irq_map[]. thoughts? - k