| To: | "Maciej W. Rozycki" <macro@linux-mips.org> |
|---|---|
| Subject: | Re: Modpost warning on Alchemy |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Thu, 2 Aug 2007 11:15:03 +0100 |
| Cc: | Sergei Shtylyov <sshtylyov@ru.mvista.com>, linux-mips@linux-mips.org |
| In-reply-to: | <Pine.LNX.4.64N.0708021024200.22591@blysk.ds.pg.gda.pl> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <46B07B36.1000501@ru.mvista.com> <Pine.LNX.4.64N.0708011337390.20314@blysk.ds.pg.gda.pl> <46B086EB.2030101@ru.mvista.com> <46B0880B.2000009@ru.mvista.com> <Pine.LNX.4.64N.0708011629010.20314@blysk.ds.pg.gda.pl> <46B0AA74.7040100@ru.mvista.com> <Pine.LNX.4.64N.0708011708250.20314@blysk.ds.pg.gda.pl> <46B0B6B4.5090103@ru.mvista.com> <46B0BE52.4000302@ru.mvista.com> <Pine.LNX.4.64N.0708021024200.22591@blysk.ds.pg.gda.pl> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.5.14 (2007-02-12) |
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 |
| Previous by Date: | Re: Modpost warning on Alchemy, Maciej W. Rozycki |
|---|---|
| Next by Date: | Re: Modpost warning on Alchemy, Maciej W. Rozycki |
| Previous by Thread: | Re: Modpost warning on Alchemy, Maciej W. Rozycki |
| Next by Thread: | Re: Modpost warning on Alchemy, Maciej W. Rozycki |
| Indexes: | [Date] [Thread] [Top] [All Lists] |