having access to interrupt specifier in map() function

[Kumar Gala]

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