Re: 2.6.17-rc5-mm1
- From: Ingo Molnar <mingo@xxxxxxx>
- Date: Wed, 31 May 2006 08:31:03 +0200
* Andrew Morton <akpm@xxxxxxxx> wrote:
Without having looked at it very hard, I'd venture that this is a
false positive - that driver uses disable_irq() to prevent reentry
onto that lock.
correct.
It does that because it knows it's about to spend a long time talking
with the mii registers and it doesn't want to do that with interrupts
disabled.
i still consider it a 'quirky' locking construct, because disabling
interrupts for a long time also disables all other devices sharing the
same IRQ line - not nice.
Also, this is a really hard case for lockdep to detect automatically.
(fortunately it's also relatively rare)
OTOH, the straightforward lockdep workaround would be to take the
spinlock and thus disable all local interrupts - not too nice either.
Albeit in some ways it's still a bit nicer conceptually than disabling
the irq line, because other CPUs are still operational, and under
certain locking designs [preempt-rt] spin_lock_irq() does not disable
local interrupts.
Steve, can you think of any better solution? I dont have this card.
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: 2.6.17-rc5-mm1
- From: Steven Rostedt
- Re: 2.6.17-rc5-mm1
- References:
- 2.6.17-rc5-mm1
- From: Andrew Morton
- Re: 2.6.17-rc5-mm1
- From: Steven Rostedt
- Re: 2.6.17-rc5-mm1
- From: Andrew Morton
- 2.6.17-rc5-mm1
- Prev by Date: [patch, -rc5-mm1] genirq MSI fixes
- Next by Date: Re: [PATCH] Add max6902 RTC support
- Previous by thread: Re: 2.6.17-rc5-mm1
- Next by thread: Re: 2.6.17-rc5-mm1
- Index(es):
Relevant Pages
|
|