Messages in this thread | | | Date | Thu, 13 Jul 2006 12:34:30 -0700 (PDT) | From | Dave Olson <> | Subject | Re: [PATCH 2/2] Initial generic hypertransport interrupt support. |
| |
On Thu, 13 Jul 2006, Eric W. Biederman wrote: | > I imagine at least some other drivers would like to know when their interrupt | > configuration changes, also, so an interface where a driver can register | > a callback handler seems like the right generic answer, or more simply, | > a way for a driver to say it doesn't want it's interrupt handler | > migrated (which we would like anyway, for performance reasons). | | As I recall that is "killall irqbalanced"
That's the way for the user or admin to do it. It would be good for a driver to be able to say "I like my interrupt here, please don't move it". It can be advisory, rather than mandatory, but there are often cases where one driver is hurt by something that is generally beneficial, and disabling it everywhere is a big hammer.
It works, but it's not ideal. Different issue than you are dealing with, but I thought it was worth bringing up, as long as we are talking about moving interrupts.
Dave Olson dave.olson@qlogic.com - 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/
| |