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
[email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH 1/2] Add Hypertransport capability defines.
    • From: [email protected] (Eric W. Biederman)
  • [PATCH 2/2] Initial generic hypertransport interrupt support.
    • From: [email protected] (Eric W. Biederman)
  • Re: [PATCH 2/2] Initial generic hypertransport interrupt support.
    • From: Andi Kleen <[email protected]>
  • Re: [PATCH 2/2] Initial generic hypertransport interrupt support.
    • From: [email protected] (Eric W. Biederman)
  • Re: [PATCH 2/2] Initial generic hypertransport interrupt support.
    • From: Dave Olson <[email protected]>
  • Re: [PATCH 2/2] Initial generic hypertransport interrupt support.
    • From: [email protected] (Eric W. Biederman)
  • Re: [PATCH 2/2] Initial generic hypertransport interrupt support.
    • From: Dave Olson <[email protected]>
  • Re: [PATCH 2/2] Initial generic hypertransport interrupt support.
    • From: [email protected] (Eric W. Biederman)
  • Re: [PATCH 2/2] Initial generic hypertransport interrupt support.
    • From: Dave Olson <[email protected]>
  • Re: [PATCH 2/2] Initial generic hypertransport interrupt support.
    • From: [email protected] (Eric W. Biederman)
  • Re: [PATCH 2/2] Initial generic hypertransport interrupt support.
    • From: Dave Olson <[email protected]>
  • Re: [PATCH 2/2] Initial generic hypertransport interrupt support.
    • From: [email protected] (Eric W. Biederman)

• Prev by Date: Re: [PATCH] ia64: race flushing icache in COW path
• Next by Date: Fwd: Using select in boolean dependents of a tristate symbol
• Previous by thread: Re: [PATCH 2/2] Initial generic hypertransport interrupt support.
• Next by thread: infiniband patch series (was Re: ipath patch series a-comin', but no IB maintainer to shepherd them)
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]