linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* having access to interrupt specifier in map() function
@ 2009-07-15 14:11 Kumar Gala
  2009-07-15 22:33 ` Benjamin Herrenschmidt
  0 siblings, 1 reply; 2+ messages in thread
From: Kumar Gala @ 2009-07-15 14:11 UTC (permalink / raw)
  To: Benjamin Herrenschmidt; +Cc: linuxppc-dev@ozlabs.org list

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2009-07-15 22:33 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-07-15 14:11 having access to interrupt specifier in map() function Kumar Gala
2009-07-15 22:33 ` Benjamin Herrenschmidt

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).