Greg KH <[EMAIL PROTECTED]> writes: > On Fri, Mar 30, 2007 at 12:47:47PM -0700, Andrew Morton wrote: >> Did we end up deciding whether this is (needed*safe) enough for 2.6.21? > > I say no for now, I have seen no bug reports for any hardware that is > not in a lab for this.
The bug report would be phrased as someone seeing "No irq for vector" on x86_64. Unless they are a skilled developer they are unlikely to trace it down to not flushing posted writes to a MSI bar during irq migration. It part it is a subtle hardware/software race. I have seen some unresolved bug reports described this way on machines that have MSI-X capable hardware. The are against fedora core and I can't haven't been able to get the reporters to try 2.6.21-rcX and the other irq back ports don't work so well. I currently count 7 drivers in 2.6.21 that are susceptible to the race this bug closes. This version of the patch seems to meet all of the criteria for being obviously correct, and all it does is insert a stupid readl. Not very dangerous. This fix removes a race between hardware and software that you likely need to migrate MSI-X irqs a lot to trigger. Which can be the kind of thing that bytes you after you have a month of uptime. This is a very nasty condition to track down from bug reports. I'd rather not have a known culprit out there. Eric - 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/