On Wed, 2006-11-15 at 10:51 -0800, Linus Torvalds wrote:
> So I think it's either: (a) irqbalance doesn't balance MSI interrupts at
> all or (b) the MSI interrupt code doesn't honor balancing requests even if
> it does.
it's (A) right now for sure for irqbalanced at least.
> The suspend problem reported by Stephen is another such thing - where MSI
> itself wasn't a problem, but stupid (probably broken) firmware code at
> wakeup broke it by an unforseen interaction. Again, that is probably
> related to the fact that nobody has ever really tested it (ie firmware
> "engineers" obviously didn't actually ever test anything with MSI enabled
> and in use, and there really is no excuse for firmware messing with the
> MSI setting - other than the usual "firmware is inevitably buggy" thing).
ok so maybe this should be in the linux firmware kit.. it has
suspend/resume tests after all ;)
if there is a "do this then this to reproduce" scenario it's even likely
it's trivial to put into a testcase...
>
> Linus
--
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
-
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/
[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]
