| commit | 735a7ffb739b6efeaeb1e720306ba308eaaeb20e | |
| author | Andrew Morton <akpm@osdl.org> | |
| Fri, 27 Oct 2006 18:42:37 +0000 (27 11:42 -0700) | ||
| committer | Linus Torvalds <torvalds@g5.osdl.org> | |
| Fri, 27 Oct 2006 22:34:51 +0000 (27 15:34 -0700) | ||
| tree | 6156c96aeae04e1fd789f07bdd839dca7eca611a | treesnapshot (tar.gz zip) |
| parent | 61ce1efe6e40233663d27ab8ac9ba9710eebcaad | commitdiff |
[PATCH] drivers: wait for threaded probes between initcall levels
The multithreaded-probing code has a problem: after one initcall level (eg,
core_initcall) has been processed, we will then start processing the next
level (postcore_initcall) while the kernel threads which are handling
core_initcall are still executing. This breaks the guarantees which the
layered initcalls previously gave us.
IOW, we want to be multithreaded _within_ an initcall level, but not between
different levels.
Fix that up by causing the probing code to wait for all outstanding probes at
one level to complete before we start processing the next level.
Cc: Greg KH <greg@kroah.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
The multithreaded-probing code has a problem: after one initcall level (eg,
core_initcall) has been processed, we will then start processing the next
level (postcore_initcall) while the kernel threads which are handling
core_initcall are still executing. This breaks the guarantees which the
layered initcalls previously gave us.
IOW, we want to be multithreaded _within_ an initcall level, but not between
different levels.
Fix that up by causing the probing code to wait for all outstanding probes at
one level to complete before we start processing the next level.
Cc: Greg KH <greg@kroah.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
| drivers/base/dd.c | diffblobblamehistory | |
| include/asm-generic/vmlinux.lds.h | diffblobblamehistory | |
| include/linux/init.h | diffblobblamehistory |