[lkml]   [2008]   [Jun]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 0/7] Boot IRQ quirks and rerouting
On Wed, 4 Jun 2008, Thomas Gleixner wrote:

> There is no way to take care of an unwanted interrupt when there is no
> handler which knows to deal with the device.

Of course.

> The problem case is mostly preempt-rt, where we receive the interrupt,
> mask it and wake up the handler thread. We can not leave it unmasked
> for obvious reasons.

Hmm, I can see what the problem is now -- you can mask the input of the
primary I/O APIC in this case (with no side effects), making other sources
at that line suffer, but at least you get away.

Anyway, my other questions remain open. How is the INTx message actually
delivered to the ICH? And why is the command line option needed?


 \ /
  Last update: 2008-06-04 19:57    [W:0.212 / U:10.008 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site