On Wed, 18 Jan 2006, Ingo Molnar wrote: > lock_cpu_hotplug() has design problems i think: hotplug-locked sections > are slowly spreading in the kernel, encompassing more and more code :-) > Shouldnt the CPU hotplug lock be a spinlock to begin with? The way it's used certainly is bizarre, but a spinlock would be harder to work with as a lot of the code protected by it sleep. - 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/
- References:
- Re: 2.6.15-mm4 failure on power5
- From: Michael Ellerman <[email protected]>
- Re: 2.6.15-mm4 failure on power5
- From: Dave C Boutcher <[email protected]>
- Re: 2.6.15-mm4 failure on power5
- From: Ingo Molnar <[email protected]>
- Re: 2.6.15-mm4 failure on power5
- From: Andrew Morton <[email protected]>
- Re: 2.6.15-mm4 failure on power5
- From: Nathan Lynch <[email protected]>
- Re: 2.6.15-mm4 failure on power5
- From: Andrew Morton <[email protected]>
- Re: 2.6.15-mm4 failure on power5
- From: Ingo Molnar <[email protected]>
- Re: 2.6.15-mm4 failure on power5
- From: Andrew Morton <[email protected]>
- [patch] turn on might_sleep() in early bootup code too
- From: Ingo Molnar <[email protected]>
- Re: [patch] turn on might_sleep() in early bootup code too
- From: Ingo Molnar <[email protected]>
- Re: 2.6.15-mm4 failure on power5
- Prev by Date: [PATCH] prototypes for *at functions & typo fix
- Next by Date: Re: [PATCH] prototypes for *at functions & typo fix
- Previous by thread: [patch] make bug messages more consistent
- Next by thread: Re: [patch] turn on might_sleep() in early bootup code too
- Index(es):
 |