On Thu, Aug 02, 2007 at 10:39:21AM +0100, Maciej W. Rozycki wrote: > > > No, I don't. But that was why the original code preferred the wired > > > entry approach over ioremap() -- not to map a whole range... > > > > Not the only one: dynamic ioremap() seems to be impossible in interrupt > > context. > > Well, ioremap() may sleep indeed. How about using a softirq then? > Broken hardware (=one that requires PCI configuration accesses from the > IRQ context) is not an excuse to extend the breakage over to software. Lockdep would trigger on ioremap from an interrupt almost immediately. But I guess not a whole lot of people are using it, probably because they think they're safe from locking problems on uniprocessors ... Ralf
