2005-04-17 02:20:36 +04:00
/*
* linux / init / main . c
*
* Copyright ( C ) 1991 , 1992 Linus Torvalds
*
* GK 2 / 5 / 95 - Changed to support mounting root fs via NFS
* Added initrd & change_root : Werner Almesberger & Hans Lermen , Feb ' 96
* Moan early if gcc is old , avoiding bogus kernels - Paul Gortmaker , May ' 96
* Simplified starting of init : Michael A . Griffith < grif @ acm . org >
*/
# include <linux/types.h>
# include <linux/module.h>
# include <linux/proc_fs.h>
# include <linux/kernel.h>
# include <linux/syscalls.h>
# include <linux/string.h>
# include <linux/ctype.h>
# include <linux/delay.h>
# include <linux/utsname.h>
# include <linux/ioport.h>
# include <linux/init.h>
# include <linux/smp_lock.h>
# include <linux/initrd.h>
# include <linux/hdreg.h>
# include <linux/bootmem.h>
# include <linux/tty.h>
# include <linux/gfp.h>
# include <linux/percpu.h>
# include <linux/kmod.h>
# include <linux/kernel_stat.h>
2006-12-07 04:14:08 +03:00
# include <linux/start_kernel.h>
2005-04-17 02:20:36 +04:00
# include <linux/security.h>
# include <linux/workqueue.h>
# include <linux/profile.h>
# include <linux/rcupdate.h>
# include <linux/moduleparam.h>
# include <linux/kallsyms.h>
# include <linux/writeback.h>
# include <linux/cpu.h>
# include <linux/cpuset.h>
# include <linux/efi.h>
2006-07-14 11:24:40 +04:00
# include <linux/taskstats_kern.h>
2006-07-14 11:24:36 +04:00
# include <linux/delayacct.h>
2005-04-17 02:20:36 +04:00
# include <linux/unistd.h>
# include <linux/rmap.h>
# include <linux/mempolicy.h>
# include <linux/key.h>
2006-06-26 15:57:28 +04:00
# include <linux/unwind.h>
2006-06-27 13:53:54 +04:00
# include <linux/buffer_head.h>
2006-07-03 11:24:33 +04:00
# include <linux/debug_locks.h>
[PATCH] lockdep: core
Do 'make oldconfig' and accept all the defaults for new config options -
reboot into the kernel and if everything goes well it should boot up fine and
you should have /proc/lockdep and /proc/lockdep_stats files.
Typically if the lock validator finds some problem it will print out
voluminous debug output that begins with "BUG: ..." and which syslog output
can be used by kernel developers to figure out the precise locking scenario.
What does the lock validator do? It "observes" and maps all locking rules as
they occur dynamically (as triggered by the kernel's natural use of spinlocks,
rwlocks, mutexes and rwsems). Whenever the lock validator subsystem detects a
new locking scenario, it validates this new rule against the existing set of
rules. If this new rule is consistent with the existing set of rules then the
new rule is added transparently and the kernel continues as normal. If the
new rule could create a deadlock scenario then this condition is printed out.
When determining validity of locking, all possible "deadlock scenarios" are
considered: assuming arbitrary number of CPUs, arbitrary irq context and task
context constellations, running arbitrary combinations of all the existing
locking scenarios. In a typical system this means millions of separate
scenarios. This is why we call it a "locking correctness" validator - for all
rules that are observed the lock validator proves it with mathematical
certainty that a deadlock could not occur (assuming that the lock validator
implementation itself is correct and its internal data structures are not
corrupted by some other kernel subsystem). [see more details and conditionals
of this statement in include/linux/lockdep.h and
Documentation/lockdep-design.txt]
Furthermore, this "all possible scenarios" property of the validator also
enables the finding of complex, highly unlikely multi-CPU multi-context races
via single single-context rules, increasing the likelyhood of finding bugs
drastically. In practical terms: the lock validator already found a bug in
the upstream kernel that could only occur on systems with 3 or more CPUs, and
which needed 3 very unlikely code sequences to occur at once on the 3 CPUs.
That bug was found and reported on a single-CPU system (!). So in essence a
race will be found "piecemail-wise", triggering all the necessary components
for the race, without having to reproduce the race scenario itself! In its
short existence the lock validator found and reported many bugs before they
actually caused a real deadlock.
To further increase the efficiency of the validator, the mapping is not per
"lock instance", but per "lock-class". For example, all struct inode objects
in the kernel have inode->inotify_mutex. If there are 10,000 inodes cached,
then there are 10,000 lock objects. But ->inotify_mutex is a single "lock
type", and all locking activities that occur against ->inotify_mutex are
"unified" into this single lock-class. The advantage of the lock-class
approach is that all historical ->inotify_mutex uses are mapped into a single
(and as narrow as possible) set of locking rules - regardless of how many
different tasks or inode structures it took to build this set of rules. The
set of rules persist during the lifetime of the kernel.
To see the rough magnitude of checking that the lock validator does, here's a
portion of /proc/lockdep_stats, fresh after bootup:
lock-classes: 694 [max: 2048]
direct dependencies: 1598 [max: 8192]
indirect dependencies: 17896
all direct dependencies: 16206
dependency chains: 1910 [max: 8192]
in-hardirq chains: 17
in-softirq chains: 105
in-process chains: 1065
stack-trace entries: 38761 [max: 131072]
combined max dependencies: 2033928
hardirq-safe locks: 24
hardirq-unsafe locks: 176
softirq-safe locks: 53
softirq-unsafe locks: 137
irq-safe locks: 59
irq-unsafe locks: 176
The lock validator has observed 1598 actual single-thread locking patterns,
and has validated all possible 2033928 distinct locking scenarios.
More details about the design of the lock validator can be found in
Documentation/lockdep-design.txt, which can also found at:
http://redhat.com/~mingo/lockdep-patches/lockdep-design.txt
[bunk@stusta.de: cleanups]
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-07-03 11:24:50 +04:00
# include <linux/lockdep.h>
2006-12-08 13:38:01 +03:00
# include <linux/pid_namespace.h>
2006-12-20 00:01:28 +03:00
# include <linux/device.h>
2005-04-17 02:20:36 +04:00
# include <asm/io.h>
# include <asm/bugs.h>
# include <asm/setup.h>
2005-07-29 08:15:30 +04:00
# include <asm/sections.h>
2006-01-06 11:12:01 +03:00
# include <asm/cacheflush.h>
2005-04-17 02:20:36 +04:00
# ifdef CONFIG_X86_LOCAL_APIC
# include <asm/smp.h>
# endif
/*
2006-01-15 00:21:11 +03:00
* This is one of the first . c files built . Error out early if we have compiler
* trouble .
*
* Versions of gcc older than that listed below may actually compile and link
* okay , but the end product can have subtle run time bugs . To avoid associated
* bogus bug reports , we flatly refuse to compile with a gcc that is known to be
* too old from the very beginning .
2005-04-17 02:20:36 +04:00
*/
2006-01-08 12:04:07 +03:00
# if (__GNUC__ < 3) || (__GNUC__ == 3 && __GNUC_MINOR__ < 2)
2005-04-17 02:20:36 +04:00
# error Sorry, your GCC is too old. It builds incorrect kernels.
# endif
2006-12-07 07:39:59 +03:00
# if __GNUC__ == 4 && __GNUC_MINOR__ == 1 && __GNUC_PATCHLEVEL__ == 0
# warning gcc-4.1.0 is known to miscompile the kernel. A different compiler version is recommended.
# endif
2005-04-17 02:20:36 +04:00
static int init ( void * ) ;
extern void init_IRQ ( void ) ;
extern void fork_init ( unsigned long ) ;
extern void mca_init ( void ) ;
extern void sbus_init ( void ) ;
extern void sysctl_init ( void ) ;
extern void signals_init ( void ) ;
extern void pidhash_init ( void ) ;
extern void pidmap_init ( void ) ;
extern void prio_tree_init ( void ) ;
extern void radix_tree_init ( void ) ;
extern void free_initmem ( void ) ;
extern void prepare_namespace ( void ) ;
# ifdef CONFIG_ACPI
extern void acpi_early_init ( void ) ;
# else
static inline void acpi_early_init ( void ) { }
# endif
2006-01-06 11:12:01 +03:00
# ifndef CONFIG_DEBUG_RODATA
static inline void mark_rodata_ro ( void ) { }
# endif
2005-04-17 02:20:36 +04:00
# ifdef CONFIG_TC
extern void tc_init ( void ) ;
# endif
enum system_states system_state ;
EXPORT_SYMBOL ( system_state ) ;
/*
* Boot command - line arguments
*/
# define MAX_INIT_ARGS CONFIG_INIT_ENV_ARG_LIMIT
# define MAX_INIT_ENVS CONFIG_INIT_ENV_ARG_LIMIT
extern void time_init ( void ) ;
/* Default late time init is NULL. archs can override this later. */
void ( * late_time_init ) ( void ) ;
extern void softirq_init ( void ) ;
/* Untouched command line (eg. for /proc) saved by arch-specific code. */
char saved_command_line [ COMMAND_LINE_SIZE ] ;
static char * execute_command ;
2005-09-07 02:17:19 +04:00
static char * ramdisk_execute_command ;
2005-04-17 02:20:36 +04:00
/* Setup configured maximum number of CPUs to activate */
static unsigned int max_cpus = NR_CPUS ;
2006-09-27 12:50:44 +04:00
/*
* If set , this is an indication to the drivers that reset the underlying
* device before going ahead with the initialization otherwise driver might
* rely on the BIOS and skip the reset operation .
*
* This is useful if kernel is booting in an unreliable environment .
* For ex . kdump situaiton where previous kernel has crashed , BIOS has been
* skipped and devices will be in unknown state .
*/
unsigned int reset_devices ;
EXPORT_SYMBOL ( reset_devices ) ;
2005-04-17 02:20:36 +04:00
/*
* Setup routine for controlling SMP activation
*
* Command - line option of " nosmp " or " maxcpus=0 " will disable SMP
* activation entirely ( the MPS table probe still happens , though ) .
*
* Command - line option of " maxcpus=<NUM> " , where < NUM > is an integer
* greater than 0 , limits the maximum number of CPUs activated in
* SMP mode to < NUM > .
*/
static int __init nosmp ( char * str )
{
max_cpus = 0 ;
return 1 ;
}
__setup ( " nosmp " , nosmp ) ;
static int __init maxcpus ( char * str )
{
get_option ( & str , & max_cpus ) ;
return 1 ;
}
__setup ( " maxcpus= " , maxcpus ) ;
2006-09-27 12:50:44 +04:00
static int __init set_reset_devices ( char * str )
{
reset_devices = 1 ;
return 1 ;
}
__setup ( " reset_devices " , set_reset_devices ) ;
2005-04-17 02:20:36 +04:00
static char * argv_init [ MAX_INIT_ARGS + 2 ] = { " init " , NULL , } ;
char * envp_init [ MAX_INIT_ENVS + 2 ] = { " HOME=/ " , " TERM=linux " , NULL , } ;
static const char * panic_later , * panic_param ;
extern struct obs_kernel_param __setup_start [ ] , __setup_end [ ] ;
static int __init obsolete_checksetup ( char * line )
{
struct obs_kernel_param * p ;
2006-09-26 12:52:32 +04:00
int had_early_param = 0 ;
2005-04-17 02:20:36 +04:00
p = __setup_start ;
do {
int n = strlen ( p - > str ) ;
if ( ! strncmp ( line , p - > str , n ) ) {
if ( p - > early ) {
2006-09-26 12:52:32 +04:00
/* Already done in parse_early_param?
* ( Needs exact match on param part ) .
* Keep iterating , as we can have early
* params and __setups of same names 8 ( */
2005-04-17 02:20:36 +04:00
if ( line [ n ] = = ' \0 ' | | line [ n ] = = ' = ' )
2006-09-26 12:52:32 +04:00
had_early_param = 1 ;
2005-04-17 02:20:36 +04:00
} else if ( ! p - > setup_func ) {
printk ( KERN_WARNING " Parameter %s is obsolete, "
" ignored \n " , p - > str ) ;
return 1 ;
} else if ( p - > setup_func ( line + n ) )
return 1 ;
}
p + + ;
} while ( p < __setup_end ) ;
2006-09-26 12:52:32 +04:00
return had_early_param ;
2005-04-17 02:20:36 +04:00
}
/*
* This should be approx 2 Bo * oMips to start ( note initial shift ) , and will
* still work even if initially too large , it will just take slightly longer
*/
unsigned long loops_per_jiffy = ( 1 < < 12 ) ;
EXPORT_SYMBOL ( loops_per_jiffy ) ;
static int __init debug_kernel ( char * str )
{
if ( * str )
return 0 ;
console_loglevel = 10 ;
return 1 ;
}
static int __init quiet_kernel ( char * str )
{
if ( * str )
return 0 ;
console_loglevel = 4 ;
return 1 ;
}
__setup ( " debug " , debug_kernel ) ;
__setup ( " quiet " , quiet_kernel ) ;
static int __init loglevel ( char * str )
{
get_option ( & str , & console_loglevel ) ;
return 1 ;
}
__setup ( " loglevel= " , loglevel ) ;
/*
* Unknown boot options get handed to init , unless they look like
* failed parameters
*/
static int __init unknown_bootoption ( char * param , char * val )
{
/* Change NUL term back to "=", to make "param" the whole string. */
if ( val ) {
/* param=val or param="val"? */
if ( val = = param + strlen ( param ) + 1 )
val [ - 1 ] = ' = ' ;
else if ( val = = param + strlen ( param ) + 2 ) {
val [ - 2 ] = ' = ' ;
memmove ( val - 1 , val , strlen ( val ) + 1 ) ;
val - - ;
} else
BUG ( ) ;
}
/* Handle obsolete-style parameters */
if ( obsolete_checksetup ( param ) )
return 0 ;
/*
* Preemptive maintenance for " why didn't my mispelled command
* line work ? "
*/
if ( strchr ( param , ' . ' ) & & ( ! val | | strchr ( param , ' . ' ) < val ) ) {
printk ( KERN_ERR " Unknown boot option `%s': ignoring \n " , param ) ;
return 0 ;
}
if ( panic_later )
return 0 ;
if ( val ) {
/* Environment option */
unsigned int i ;
for ( i = 0 ; envp_init [ i ] ; i + + ) {
if ( i = = MAX_INIT_ENVS ) {
panic_later = " Too many boot env vars at `%s' " ;
panic_param = param ;
}
if ( ! strncmp ( param , envp_init [ i ] , val - param ) )
break ;
}
envp_init [ i ] = param ;
} else {
/* Command line option */
unsigned int i ;
for ( i = 0 ; argv_init [ i ] ; i + + ) {
if ( i = = MAX_INIT_ARGS ) {
panic_later = " Too many boot init vars at `%s' " ;
panic_param = param ;
}
}
argv_init [ i ] = param ;
}
return 0 ;
}
static int __init init_setup ( char * str )
{
unsigned int i ;
execute_command = str ;
/*
* In case LILO is going to boot us with default command line ,
* it prepends " auto " before the whole cmdline which makes
* the shell think it should execute a script with such name .
* So we ignore all arguments entered _before_ init = . . . [ MJ ]
*/
for ( i = 1 ; i < MAX_INIT_ARGS ; i + + )
argv_init [ i ] = NULL ;
return 1 ;
}
__setup ( " init= " , init_setup ) ;
2005-09-07 02:17:19 +04:00
static int __init rdinit_setup ( char * str )
{
unsigned int i ;
ramdisk_execute_command = str ;
/* See "auto" comment in init_setup */
for ( i = 1 ; i < MAX_INIT_ARGS ; i + + )
argv_init [ i ] = NULL ;
return 1 ;
}
__setup ( " rdinit= " , rdinit_setup ) ;
2005-04-17 02:20:36 +04:00
# ifndef CONFIG_SMP
# ifdef CONFIG_X86_LOCAL_APIC
static void __init smp_init ( void )
{
APIC_init_uniprocessor ( ) ;
}
# else
# define smp_init() do { } while (0)
# endif
static inline void setup_per_cpu_areas ( void ) { }
static inline void smp_prepare_cpus ( unsigned int maxcpus ) { }
# else
# ifdef __GENERIC_PER_CPU
2006-03-23 14:01:07 +03:00
unsigned long __per_cpu_offset [ NR_CPUS ] __read_mostly ;
2005-04-17 02:20:36 +04:00
EXPORT_SYMBOL ( __per_cpu_offset ) ;
static void __init setup_per_cpu_areas ( void )
{
unsigned long size , i ;
char * ptr ;
2006-03-23 14:01:04 +03:00
unsigned long nr_possible_cpus = num_possible_cpus ( ) ;
2005-04-17 02:20:36 +04:00
/* Copy section for each CPU (we discard the original) */
size = ALIGN ( __per_cpu_end - __per_cpu_start , SMP_CACHE_BYTES ) ;
# ifdef CONFIG_MODULES
if ( size < PERCPU_ENOUGH_ROOM )
size = PERCPU_ENOUGH_ROOM ;
# endif
2006-03-23 14:01:04 +03:00
ptr = alloc_bootmem ( size * nr_possible_cpus ) ;
2005-04-17 02:20:36 +04:00
2006-03-28 13:56:37 +04:00
for_each_possible_cpu ( i ) {
2005-04-17 02:20:36 +04:00
__per_cpu_offset [ i ] = ptr - __per_cpu_start ;
memcpy ( ptr , __per_cpu_start , __per_cpu_end - __per_cpu_start ) ;
2006-03-23 14:01:04 +03:00
ptr + = size ;
2005-04-17 02:20:36 +04:00
}
}
# endif /* !__GENERIC_PER_CPU */
/* Called by boot processor to activate the rest. */
static void __init smp_init ( void )
{
unsigned int i ;
/* FIXME: This should be done in userspace --RR */
for_each_present_cpu ( i ) {
if ( num_online_cpus ( ) > = max_cpus )
break ;
if ( ! cpu_online ( i ) )
cpu_up ( i ) ;
}
/* Any cleanup work */
printk ( KERN_INFO " Brought up %ld CPUs \n " , ( long ) num_online_cpus ( ) ) ;
smp_cpus_done ( max_cpus ) ;
}
# endif
/*
* We need to finalize in a non - __init function or else race conditions
* between the root thread and the init thread may cause start_kernel to
* be reaped by free_initmem before the root thread has proceeded to
* cpu_idle .
*
* gcc - 3.4 accidentally inlines this function , so use noinline .
*/
static void noinline rest_init ( void )
__releases ( kernel_lock )
{
kernel_thread ( init , NULL , CLONE_FS | CLONE_SIGHAND ) ;
numa_default_policy ( ) ;
unlock_kernel ( ) ;
2005-06-28 18:40:42 +04:00
/*
* The boot idle thread must execute schedule ( )
* at least one to get things moving :
*/
2005-11-09 08:39:01 +03:00
preempt_enable_no_resched ( ) ;
2005-06-28 18:40:42 +04:00
schedule ( ) ;
2005-11-09 08:39:01 +03:00
preempt_disable ( ) ;
2005-06-28 18:40:42 +04:00
2005-11-09 08:39:01 +03:00
/* Call into cpu_idle with preempt disabled */
2005-04-17 02:20:36 +04:00
cpu_idle ( ) ;
}
/* Check for early params. */
static int __init do_early_param ( char * param , char * val )
{
struct obs_kernel_param * p ;
for ( p = __setup_start ; p < __setup_end ; p + + ) {
if ( p - > early & & strcmp ( param , p - > str ) = = 0 ) {
if ( p - > setup_func ( val ) ! = 0 )
printk ( KERN_WARNING
" Malformed early option '%s' \n " , param ) ;
}
}
/* We accept everything at this stage. */
return 0 ;
}
/* Arch code calls this early on, or if not, just before other parsing. */
void __init parse_early_param ( void )
{
static __initdata int done = 0 ;
static __initdata char tmp_cmdline [ COMMAND_LINE_SIZE ] ;
if ( done )
return ;
/* All fall through to do_early_param. */
strlcpy ( tmp_cmdline , saved_command_line , COMMAND_LINE_SIZE ) ;
parse_args ( " early options " , tmp_cmdline , NULL , 0 , do_early_param ) ;
done = 1 ;
}
/*
* Activate the first processor .
*/
2006-03-23 13:59:44 +03:00
static void __init boot_cpu_init ( void )
{
int cpu = smp_processor_id ( ) ;
/* Mark the boot cpu "present", "online" etc for SMP and UP case */
cpu_set ( cpu , cpu_online_map ) ;
cpu_set ( cpu , cpu_present_map ) ;
cpu_set ( cpu , cpu_possible_map ) ;
}
2006-06-30 12:55:50 +04:00
void __init __attribute__ ( ( weak ) ) smp_setup_processor_id ( void )
{
}
2005-04-17 02:20:36 +04:00
asmlinkage void __init start_kernel ( void )
{
char * command_line ;
extern struct kernel_param __start___param [ ] , __stop___param [ ] ;
2006-06-30 12:55:50 +04:00
smp_setup_processor_id ( ) ;
[PATCH] lockdep: core
Do 'make oldconfig' and accept all the defaults for new config options -
reboot into the kernel and if everything goes well it should boot up fine and
you should have /proc/lockdep and /proc/lockdep_stats files.
Typically if the lock validator finds some problem it will print out
voluminous debug output that begins with "BUG: ..." and which syslog output
can be used by kernel developers to figure out the precise locking scenario.
What does the lock validator do? It "observes" and maps all locking rules as
they occur dynamically (as triggered by the kernel's natural use of spinlocks,
rwlocks, mutexes and rwsems). Whenever the lock validator subsystem detects a
new locking scenario, it validates this new rule against the existing set of
rules. If this new rule is consistent with the existing set of rules then the
new rule is added transparently and the kernel continues as normal. If the
new rule could create a deadlock scenario then this condition is printed out.
When determining validity of locking, all possible "deadlock scenarios" are
considered: assuming arbitrary number of CPUs, arbitrary irq context and task
context constellations, running arbitrary combinations of all the existing
locking scenarios. In a typical system this means millions of separate
scenarios. This is why we call it a "locking correctness" validator - for all
rules that are observed the lock validator proves it with mathematical
certainty that a deadlock could not occur (assuming that the lock validator
implementation itself is correct and its internal data structures are not
corrupted by some other kernel subsystem). [see more details and conditionals
of this statement in include/linux/lockdep.h and
Documentation/lockdep-design.txt]
Furthermore, this "all possible scenarios" property of the validator also
enables the finding of complex, highly unlikely multi-CPU multi-context races
via single single-context rules, increasing the likelyhood of finding bugs
drastically. In practical terms: the lock validator already found a bug in
the upstream kernel that could only occur on systems with 3 or more CPUs, and
which needed 3 very unlikely code sequences to occur at once on the 3 CPUs.
That bug was found and reported on a single-CPU system (!). So in essence a
race will be found "piecemail-wise", triggering all the necessary components
for the race, without having to reproduce the race scenario itself! In its
short existence the lock validator found and reported many bugs before they
actually caused a real deadlock.
To further increase the efficiency of the validator, the mapping is not per
"lock instance", but per "lock-class". For example, all struct inode objects
in the kernel have inode->inotify_mutex. If there are 10,000 inodes cached,
then there are 10,000 lock objects. But ->inotify_mutex is a single "lock
type", and all locking activities that occur against ->inotify_mutex are
"unified" into this single lock-class. The advantage of the lock-class
approach is that all historical ->inotify_mutex uses are mapped into a single
(and as narrow as possible) set of locking rules - regardless of how many
different tasks or inode structures it took to build this set of rules. The
set of rules persist during the lifetime of the kernel.
To see the rough magnitude of checking that the lock validator does, here's a
portion of /proc/lockdep_stats, fresh after bootup:
lock-classes: 694 [max: 2048]
direct dependencies: 1598 [max: 8192]
indirect dependencies: 17896
all direct dependencies: 16206
dependency chains: 1910 [max: 8192]
in-hardirq chains: 17
in-softirq chains: 105
in-process chains: 1065
stack-trace entries: 38761 [max: 131072]
combined max dependencies: 2033928
hardirq-safe locks: 24
hardirq-unsafe locks: 176
softirq-safe locks: 53
softirq-unsafe locks: 137
irq-safe locks: 59
irq-unsafe locks: 176
The lock validator has observed 1598 actual single-thread locking patterns,
and has validated all possible 2033928 distinct locking scenarios.
More details about the design of the lock validator can be found in
Documentation/lockdep-design.txt, which can also found at:
http://redhat.com/~mingo/lockdep-patches/lockdep-design.txt
[bunk@stusta.de: cleanups]
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-07-03 11:24:50 +04:00
/*
* Need to run as early as possible , to initialize the
* lockdep hash :
*/
2006-09-26 12:52:34 +04:00
unwind_init ( ) ;
[PATCH] lockdep: core
Do 'make oldconfig' and accept all the defaults for new config options -
reboot into the kernel and if everything goes well it should boot up fine and
you should have /proc/lockdep and /proc/lockdep_stats files.
Typically if the lock validator finds some problem it will print out
voluminous debug output that begins with "BUG: ..." and which syslog output
can be used by kernel developers to figure out the precise locking scenario.
What does the lock validator do? It "observes" and maps all locking rules as
they occur dynamically (as triggered by the kernel's natural use of spinlocks,
rwlocks, mutexes and rwsems). Whenever the lock validator subsystem detects a
new locking scenario, it validates this new rule against the existing set of
rules. If this new rule is consistent with the existing set of rules then the
new rule is added transparently and the kernel continues as normal. If the
new rule could create a deadlock scenario then this condition is printed out.
When determining validity of locking, all possible "deadlock scenarios" are
considered: assuming arbitrary number of CPUs, arbitrary irq context and task
context constellations, running arbitrary combinations of all the existing
locking scenarios. In a typical system this means millions of separate
scenarios. This is why we call it a "locking correctness" validator - for all
rules that are observed the lock validator proves it with mathematical
certainty that a deadlock could not occur (assuming that the lock validator
implementation itself is correct and its internal data structures are not
corrupted by some other kernel subsystem). [see more details and conditionals
of this statement in include/linux/lockdep.h and
Documentation/lockdep-design.txt]
Furthermore, this "all possible scenarios" property of the validator also
enables the finding of complex, highly unlikely multi-CPU multi-context races
via single single-context rules, increasing the likelyhood of finding bugs
drastically. In practical terms: the lock validator already found a bug in
the upstream kernel that could only occur on systems with 3 or more CPUs, and
which needed 3 very unlikely code sequences to occur at once on the 3 CPUs.
That bug was found and reported on a single-CPU system (!). So in essence a
race will be found "piecemail-wise", triggering all the necessary components
for the race, without having to reproduce the race scenario itself! In its
short existence the lock validator found and reported many bugs before they
actually caused a real deadlock.
To further increase the efficiency of the validator, the mapping is not per
"lock instance", but per "lock-class". For example, all struct inode objects
in the kernel have inode->inotify_mutex. If there are 10,000 inodes cached,
then there are 10,000 lock objects. But ->inotify_mutex is a single "lock
type", and all locking activities that occur against ->inotify_mutex are
"unified" into this single lock-class. The advantage of the lock-class
approach is that all historical ->inotify_mutex uses are mapped into a single
(and as narrow as possible) set of locking rules - regardless of how many
different tasks or inode structures it took to build this set of rules. The
set of rules persist during the lifetime of the kernel.
To see the rough magnitude of checking that the lock validator does, here's a
portion of /proc/lockdep_stats, fresh after bootup:
lock-classes: 694 [max: 2048]
direct dependencies: 1598 [max: 8192]
indirect dependencies: 17896
all direct dependencies: 16206
dependency chains: 1910 [max: 8192]
in-hardirq chains: 17
in-softirq chains: 105
in-process chains: 1065
stack-trace entries: 38761 [max: 131072]
combined max dependencies: 2033928
hardirq-safe locks: 24
hardirq-unsafe locks: 176
softirq-safe locks: 53
softirq-unsafe locks: 137
irq-safe locks: 59
irq-unsafe locks: 176
The lock validator has observed 1598 actual single-thread locking patterns,
and has validated all possible 2033928 distinct locking scenarios.
More details about the design of the lock validator can be found in
Documentation/lockdep-design.txt, which can also found at:
http://redhat.com/~mingo/lockdep-patches/lockdep-design.txt
[bunk@stusta.de: cleanups]
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-07-03 11:24:50 +04:00
lockdep_init ( ) ;
local_irq_disable ( ) ;
early_boot_irqs_off ( ) ;
2006-07-03 11:25:06 +04:00
early_init_irq_lock_class ( ) ;
[PATCH] lockdep: core
Do 'make oldconfig' and accept all the defaults for new config options -
reboot into the kernel and if everything goes well it should boot up fine and
you should have /proc/lockdep and /proc/lockdep_stats files.
Typically if the lock validator finds some problem it will print out
voluminous debug output that begins with "BUG: ..." and which syslog output
can be used by kernel developers to figure out the precise locking scenario.
What does the lock validator do? It "observes" and maps all locking rules as
they occur dynamically (as triggered by the kernel's natural use of spinlocks,
rwlocks, mutexes and rwsems). Whenever the lock validator subsystem detects a
new locking scenario, it validates this new rule against the existing set of
rules. If this new rule is consistent with the existing set of rules then the
new rule is added transparently and the kernel continues as normal. If the
new rule could create a deadlock scenario then this condition is printed out.
When determining validity of locking, all possible "deadlock scenarios" are
considered: assuming arbitrary number of CPUs, arbitrary irq context and task
context constellations, running arbitrary combinations of all the existing
locking scenarios. In a typical system this means millions of separate
scenarios. This is why we call it a "locking correctness" validator - for all
rules that are observed the lock validator proves it with mathematical
certainty that a deadlock could not occur (assuming that the lock validator
implementation itself is correct and its internal data structures are not
corrupted by some other kernel subsystem). [see more details and conditionals
of this statement in include/linux/lockdep.h and
Documentation/lockdep-design.txt]
Furthermore, this "all possible scenarios" property of the validator also
enables the finding of complex, highly unlikely multi-CPU multi-context races
via single single-context rules, increasing the likelyhood of finding bugs
drastically. In practical terms: the lock validator already found a bug in
the upstream kernel that could only occur on systems with 3 or more CPUs, and
which needed 3 very unlikely code sequences to occur at once on the 3 CPUs.
That bug was found and reported on a single-CPU system (!). So in essence a
race will be found "piecemail-wise", triggering all the necessary components
for the race, without having to reproduce the race scenario itself! In its
short existence the lock validator found and reported many bugs before they
actually caused a real deadlock.
To further increase the efficiency of the validator, the mapping is not per
"lock instance", but per "lock-class". For example, all struct inode objects
in the kernel have inode->inotify_mutex. If there are 10,000 inodes cached,
then there are 10,000 lock objects. But ->inotify_mutex is a single "lock
type", and all locking activities that occur against ->inotify_mutex are
"unified" into this single lock-class. The advantage of the lock-class
approach is that all historical ->inotify_mutex uses are mapped into a single
(and as narrow as possible) set of locking rules - regardless of how many
different tasks or inode structures it took to build this set of rules. The
set of rules persist during the lifetime of the kernel.
To see the rough magnitude of checking that the lock validator does, here's a
portion of /proc/lockdep_stats, fresh after bootup:
lock-classes: 694 [max: 2048]
direct dependencies: 1598 [max: 8192]
indirect dependencies: 17896
all direct dependencies: 16206
dependency chains: 1910 [max: 8192]
in-hardirq chains: 17
in-softirq chains: 105
in-process chains: 1065
stack-trace entries: 38761 [max: 131072]
combined max dependencies: 2033928
hardirq-safe locks: 24
hardirq-unsafe locks: 176
softirq-safe locks: 53
softirq-unsafe locks: 137
irq-safe locks: 59
irq-unsafe locks: 176
The lock validator has observed 1598 actual single-thread locking patterns,
and has validated all possible 2033928 distinct locking scenarios.
More details about the design of the lock validator can be found in
Documentation/lockdep-design.txt, which can also found at:
http://redhat.com/~mingo/lockdep-patches/lockdep-design.txt
[bunk@stusta.de: cleanups]
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-07-03 11:24:50 +04:00
2005-04-17 02:20:36 +04:00
/*
* Interrupts are still disabled . Do necessary setups , then
* enable them
*/
lock_kernel ( ) ;
2006-03-23 13:59:44 +03:00
boot_cpu_init ( ) ;
2005-04-17 02:20:36 +04:00
page_address_init ( ) ;
printk ( KERN_NOTICE ) ;
2006-12-11 20:28:46 +03:00
printk ( linux_banner ) ;
2005-04-17 02:20:36 +04:00
setup_arch ( & command_line ) ;
2006-10-21 20:37:01 +04:00
unwind_setup ( ) ;
2005-04-17 02:20:36 +04:00
setup_per_cpu_areas ( ) ;
2006-03-23 13:59:44 +03:00
smp_prepare_boot_cpu ( ) ; /* arch-specific boot-cpu hooks */
2005-04-17 02:20:36 +04:00
/*
* Set up the scheduler prior starting any interrupts ( such as the
* timer interrupt ) . Full topology setup happens at smp_init ( )
* time - but meanwhile we still have a functioning scheduler .
*/
sched_init ( ) ;
/*
* Disable preemption - early bootup scheduling is extremely
* fragile until we cpu_idle ( ) for the first time .
*/
preempt_disable ( ) ;
build_all_zonelists ( ) ;
page_alloc_init ( ) ;
printk ( KERN_NOTICE " Kernel command line: %s \n " , saved_command_line ) ;
parse_early_param ( ) ;
parse_args ( " Booting kernel " , command_line , __start___param ,
__stop___param - __start___param ,
& unknown_bootoption ) ;
2007-01-06 03:36:19 +03:00
if ( ! irqs_disabled ( ) ) {
printk ( KERN_WARNING " start_kernel(): bug: interrupts were "
" enabled *very* early, fixing it \n " ) ;
local_irq_disable ( ) ;
}
2005-04-17 02:20:36 +04:00
sort_main_extable ( ) ;
trap_init ( ) ;
rcu_init ( ) ;
init_IRQ ( ) ;
pidhash_init ( ) ;
init_timers ( ) ;
2006-01-10 07:52:32 +03:00
hrtimers_init ( ) ;
2005-04-17 02:20:36 +04:00
softirq_init ( ) ;
2006-06-26 11:25:06 +04:00
timekeeping_init ( ) ;
2006-07-03 11:24:04 +04:00
time_init ( ) ;
2006-07-03 11:24:24 +04:00
profile_init ( ) ;
if ( ! irqs_disabled ( ) )
printk ( " start_kernel(): bug: interrupts were enabled early \n " ) ;
[PATCH] lockdep: core
Do 'make oldconfig' and accept all the defaults for new config options -
reboot into the kernel and if everything goes well it should boot up fine and
you should have /proc/lockdep and /proc/lockdep_stats files.
Typically if the lock validator finds some problem it will print out
voluminous debug output that begins with "BUG: ..." and which syslog output
can be used by kernel developers to figure out the precise locking scenario.
What does the lock validator do? It "observes" and maps all locking rules as
they occur dynamically (as triggered by the kernel's natural use of spinlocks,
rwlocks, mutexes and rwsems). Whenever the lock validator subsystem detects a
new locking scenario, it validates this new rule against the existing set of
rules. If this new rule is consistent with the existing set of rules then the
new rule is added transparently and the kernel continues as normal. If the
new rule could create a deadlock scenario then this condition is printed out.
When determining validity of locking, all possible "deadlock scenarios" are
considered: assuming arbitrary number of CPUs, arbitrary irq context and task
context constellations, running arbitrary combinations of all the existing
locking scenarios. In a typical system this means millions of separate
scenarios. This is why we call it a "locking correctness" validator - for all
rules that are observed the lock validator proves it with mathematical
certainty that a deadlock could not occur (assuming that the lock validator
implementation itself is correct and its internal data structures are not
corrupted by some other kernel subsystem). [see more details and conditionals
of this statement in include/linux/lockdep.h and
Documentation/lockdep-design.txt]
Furthermore, this "all possible scenarios" property of the validator also
enables the finding of complex, highly unlikely multi-CPU multi-context races
via single single-context rules, increasing the likelyhood of finding bugs
drastically. In practical terms: the lock validator already found a bug in
the upstream kernel that could only occur on systems with 3 or more CPUs, and
which needed 3 very unlikely code sequences to occur at once on the 3 CPUs.
That bug was found and reported on a single-CPU system (!). So in essence a
race will be found "piecemail-wise", triggering all the necessary components
for the race, without having to reproduce the race scenario itself! In its
short existence the lock validator found and reported many bugs before they
actually caused a real deadlock.
To further increase the efficiency of the validator, the mapping is not per
"lock instance", but per "lock-class". For example, all struct inode objects
in the kernel have inode->inotify_mutex. If there are 10,000 inodes cached,
then there are 10,000 lock objects. But ->inotify_mutex is a single "lock
type", and all locking activities that occur against ->inotify_mutex are
"unified" into this single lock-class. The advantage of the lock-class
approach is that all historical ->inotify_mutex uses are mapped into a single
(and as narrow as possible) set of locking rules - regardless of how many
different tasks or inode structures it took to build this set of rules. The
set of rules persist during the lifetime of the kernel.
To see the rough magnitude of checking that the lock validator does, here's a
portion of /proc/lockdep_stats, fresh after bootup:
lock-classes: 694 [max: 2048]
direct dependencies: 1598 [max: 8192]
indirect dependencies: 17896
all direct dependencies: 16206
dependency chains: 1910 [max: 8192]
in-hardirq chains: 17
in-softirq chains: 105
in-process chains: 1065
stack-trace entries: 38761 [max: 131072]
combined max dependencies: 2033928
hardirq-safe locks: 24
hardirq-unsafe locks: 176
softirq-safe locks: 53
softirq-unsafe locks: 137
irq-safe locks: 59
irq-unsafe locks: 176
The lock validator has observed 1598 actual single-thread locking patterns,
and has validated all possible 2033928 distinct locking scenarios.
More details about the design of the lock validator can be found in
Documentation/lockdep-design.txt, which can also found at:
http://redhat.com/~mingo/lockdep-patches/lockdep-design.txt
[bunk@stusta.de: cleanups]
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-07-03 11:24:50 +04:00
early_boot_irqs_on ( ) ;
2006-07-03 11:24:24 +04:00
local_irq_enable ( ) ;
2005-04-17 02:20:36 +04:00
/*
* HACK ALERT ! This is early . We ' re enabling the console before
* we ' ve done PCI setups etc , and console_init ( ) must be aware of
* this . But we do want output early , in case something goes wrong .
*/
console_init ( ) ;
if ( panic_later )
panic ( panic_later , panic_param ) ;
[PATCH] lockdep: core
Do 'make oldconfig' and accept all the defaults for new config options -
reboot into the kernel and if everything goes well it should boot up fine and
you should have /proc/lockdep and /proc/lockdep_stats files.
Typically if the lock validator finds some problem it will print out
voluminous debug output that begins with "BUG: ..." and which syslog output
can be used by kernel developers to figure out the precise locking scenario.
What does the lock validator do? It "observes" and maps all locking rules as
they occur dynamically (as triggered by the kernel's natural use of spinlocks,
rwlocks, mutexes and rwsems). Whenever the lock validator subsystem detects a
new locking scenario, it validates this new rule against the existing set of
rules. If this new rule is consistent with the existing set of rules then the
new rule is added transparently and the kernel continues as normal. If the
new rule could create a deadlock scenario then this condition is printed out.
When determining validity of locking, all possible "deadlock scenarios" are
considered: assuming arbitrary number of CPUs, arbitrary irq context and task
context constellations, running arbitrary combinations of all the existing
locking scenarios. In a typical system this means millions of separate
scenarios. This is why we call it a "locking correctness" validator - for all
rules that are observed the lock validator proves it with mathematical
certainty that a deadlock could not occur (assuming that the lock validator
implementation itself is correct and its internal data structures are not
corrupted by some other kernel subsystem). [see more details and conditionals
of this statement in include/linux/lockdep.h and
Documentation/lockdep-design.txt]
Furthermore, this "all possible scenarios" property of the validator also
enables the finding of complex, highly unlikely multi-CPU multi-context races
via single single-context rules, increasing the likelyhood of finding bugs
drastically. In practical terms: the lock validator already found a bug in
the upstream kernel that could only occur on systems with 3 or more CPUs, and
which needed 3 very unlikely code sequences to occur at once on the 3 CPUs.
That bug was found and reported on a single-CPU system (!). So in essence a
race will be found "piecemail-wise", triggering all the necessary components
for the race, without having to reproduce the race scenario itself! In its
short existence the lock validator found and reported many bugs before they
actually caused a real deadlock.
To further increase the efficiency of the validator, the mapping is not per
"lock instance", but per "lock-class". For example, all struct inode objects
in the kernel have inode->inotify_mutex. If there are 10,000 inodes cached,
then there are 10,000 lock objects. But ->inotify_mutex is a single "lock
type", and all locking activities that occur against ->inotify_mutex are
"unified" into this single lock-class. The advantage of the lock-class
approach is that all historical ->inotify_mutex uses are mapped into a single
(and as narrow as possible) set of locking rules - regardless of how many
different tasks or inode structures it took to build this set of rules. The
set of rules persist during the lifetime of the kernel.
To see the rough magnitude of checking that the lock validator does, here's a
portion of /proc/lockdep_stats, fresh after bootup:
lock-classes: 694 [max: 2048]
direct dependencies: 1598 [max: 8192]
indirect dependencies: 17896
all direct dependencies: 16206
dependency chains: 1910 [max: 8192]
in-hardirq chains: 17
in-softirq chains: 105
in-process chains: 1065
stack-trace entries: 38761 [max: 131072]
combined max dependencies: 2033928
hardirq-safe locks: 24
hardirq-unsafe locks: 176
softirq-safe locks: 53
softirq-unsafe locks: 137
irq-safe locks: 59
irq-unsafe locks: 176
The lock validator has observed 1598 actual single-thread locking patterns,
and has validated all possible 2033928 distinct locking scenarios.
More details about the design of the lock validator can be found in
Documentation/lockdep-design.txt, which can also found at:
http://redhat.com/~mingo/lockdep-patches/lockdep-design.txt
[bunk@stusta.de: cleanups]
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-07-03 11:24:50 +04:00
lockdep_info ( ) ;
2006-07-03 11:24:33 +04:00
/*
* Need to run this when irqs are enabled , because it wants
* to self - test [ hard / soft ] - irqs on / off lock inversion bugs
* too :
*/
locking_selftest ( ) ;
2005-04-17 02:20:36 +04:00
# ifdef CONFIG_BLK_DEV_INITRD
if ( initrd_start & & ! initrd_below_start_ok & &
initrd_start < min_low_pfn < < PAGE_SHIFT ) {
printk ( KERN_CRIT " initrd overwritten (0x%08lx < 0x%08lx) - "
" disabling it. \n " , initrd_start , min_low_pfn < < PAGE_SHIFT ) ;
initrd_start = 0 ;
}
# endif
vfs_caches_init_early ( ) ;
2006-01-08 12:02:01 +03:00
cpuset_init_early ( ) ;
2005-04-17 02:20:36 +04:00
mem_init ( ) ;
kmem_cache_init ( ) ;
2005-06-22 04:14:47 +04:00
setup_per_cpu_pageset ( ) ;
2005-04-17 02:20:36 +04:00
numa_policy_init ( ) ;
if ( late_time_init )
late_time_init ( ) ;
calibrate_delay ( ) ;
pidmap_init ( ) ;
pgtable_cache_init ( ) ;
prio_tree_init ( ) ;
anon_vma_init ( ) ;
# ifdef CONFIG_X86
if ( efi_enabled )
efi_enter_virtual_mode ( ) ;
# endif
fork_init ( num_physpages ) ;
proc_caches_init ( ) ;
buffer_init ( ) ;
unnamed_dev_init ( ) ;
key_init ( ) ;
security_init ( ) ;
vfs_caches_init ( num_physpages ) ;
radix_tree_init ( ) ;
signals_init ( ) ;
/* rootfs populating might need page-writeback */
page_writeback_init ( ) ;
# ifdef CONFIG_PROC_FS
proc_root_init ( ) ;
# endif
cpuset_init ( ) ;
2006-07-14 11:24:40 +04:00
taskstats_init_early ( ) ;
2006-07-14 11:24:36 +04:00
delayacct_init ( ) ;
2005-04-17 02:20:36 +04:00
check_bugs ( ) ;
acpi_early_init ( ) ; /* before LAPIC and SMP init */
/* Do the rest non-__init'ed, we're now alive */
rest_init ( ) ;
}
static int __initdata initcall_debug ;
static int __init initcall_debug_setup ( char * str )
{
initcall_debug = 1 ;
return 1 ;
}
__setup ( " initcall_debug " , initcall_debug_setup ) ;
extern initcall_t __initcall_start [ ] , __initcall_end [ ] ;
static void __init do_initcalls ( void )
{
initcall_t * call ;
int count = preempt_count ( ) ;
for ( call = __initcall_start ; call < __initcall_end ; call + + ) {
2006-03-25 14:07:15 +03:00
char * msg = NULL ;
char msgbuf [ 40 ] ;
int result ;
2005-04-17 02:20:36 +04:00
if ( initcall_debug ) {
2006-03-25 14:07:15 +03:00
printk ( " Calling initcall 0x%p " , * call ) ;
print_fn_descriptor_symbol ( " : %s() " ,
( unsigned long ) * call ) ;
2005-04-17 02:20:36 +04:00
printk ( " \n " ) ;
}
2006-03-25 14:07:15 +03:00
result = ( * call ) ( ) ;
2005-04-17 02:20:36 +04:00
2006-05-01 23:15:52 +04:00
if ( result & & result ! = - ENODEV & & initcall_debug ) {
2006-03-25 14:07:15 +03:00
sprintf ( msgbuf , " error code %d " , result ) ;
msg = msgbuf ;
}
2005-04-17 02:20:36 +04:00
if ( preempt_count ( ) ! = count ) {
msg = " preemption imbalance " ;
preempt_count ( ) = count ;
}
if ( irqs_disabled ( ) ) {
msg = " disabled interrupts " ;
local_irq_enable ( ) ;
}
if ( msg ) {
2006-03-25 14:07:15 +03:00
printk ( KERN_WARNING " initcall at 0x%p " , * call ) ;
print_fn_descriptor_symbol ( " : %s() " ,
( unsigned long ) * call ) ;
printk ( " : returned with %s \n " , msg ) ;
2005-04-17 02:20:36 +04:00
}
}
/* Make sure there is no pending stuff from the initcall sequence */
flush_scheduled_work ( ) ;
}
/*
* Ok , the machine is now initialized . None of the devices
* have been touched yet , but the CPU subsystem is up and
* running , and memory and process management works .
*
* Now we can finally start doing some real work . .
*/
static void __init do_basic_setup ( void )
{
/* drivers will send hotplug events */
init_workqueues ( ) ;
usermodehelper_init ( ) ;
driver_init ( ) ;
# ifdef CONFIG_SYSCTL
sysctl_init ( ) ;
# endif
do_initcalls ( ) ;
}
2007-01-11 03:52:44 +03:00
static void __init do_pre_smp_initcalls ( void )
2005-04-17 02:20:36 +04:00
{
extern int spawn_ksoftirqd ( void ) ;
# ifdef CONFIG_SMP
extern int migration_init ( void ) ;
migration_init ( ) ;
# endif
spawn_ksoftirqd ( ) ;
2005-09-07 02:16:27 +04:00
spawn_softlockup_task ( ) ;
2005-04-17 02:20:36 +04:00
}
static void run_init_process ( char * init_filename )
{
argv_init [ 0 ] = init_filename ;
2006-10-02 13:18:26 +04:00
kernel_execve ( init_filename , argv_init , envp_init ) ;
2005-04-17 02:20:36 +04:00
}
static int init ( void * unused )
{
lock_kernel ( ) ;
/*
* init can run on any cpu .
*/
set_cpus_allowed ( current , CPU_MASK_ALL ) ;
/*
* Tell the world that we ' re going to be the grim
* reaper of innocent orphaned children .
*
* We don ' t want people to have to make incorrect
* assumptions about where in the task array this
* can be found .
*/
2006-12-08 13:38:01 +03:00
init_pid_ns . child_reaper = current ;
2005-04-17 02:20:36 +04:00
2006-10-02 13:19:00 +04:00
cad_pid = task_pid ( current ) ;
2005-04-17 02:20:36 +04:00
smp_prepare_cpus ( max_cpus ) ;
do_pre_smp_initcalls ( ) ;
smp_init ( ) ;
sched_init_smp ( ) ;
cpuset_init_smp ( ) ;
do_basic_setup ( ) ;
/*
* check if there is an early userspace init . If yes , let it do all
* the work
*/
2005-09-07 02:17:19 +04:00
if ( ! ramdisk_execute_command )
ramdisk_execute_command = " /init " ;
if ( sys_access ( ( const char __user * ) ramdisk_execute_command , 0 ) ! = 0 ) {
ramdisk_execute_command = NULL ;
2005-04-17 02:20:36 +04:00
prepare_namespace ( ) ;
2005-09-07 02:17:19 +04:00
}
2005-04-17 02:20:36 +04:00
/*
* Ok , we have completed the initial bootup , and
* we ' re essentially up and running . Get rid of the
* initmem segments and start the user - mode stuff . .
*/
free_initmem ( ) ;
unlock_kernel ( ) ;
2006-01-06 11:12:01 +03:00
mark_rodata_ro ( ) ;
2005-04-17 02:20:36 +04:00
system_state = SYSTEM_RUNNING ;
numa_default_policy ( ) ;
if ( sys_open ( ( const char __user * ) " /dev/console " , O_RDWR , 0 ) < 0 )
printk ( KERN_WARNING " Warning: unable to open an initial console. \n " ) ;
( void ) sys_dup ( 0 ) ;
( void ) sys_dup ( 0 ) ;
2005-09-07 02:17:19 +04:00
if ( ramdisk_execute_command ) {
run_init_process ( ramdisk_execute_command ) ;
printk ( KERN_WARNING " Failed to execute %s \n " ,
ramdisk_execute_command ) ;
}
2005-04-17 02:20:36 +04:00
/*
* We try each of these until one succeeds .
*
* The Bourne shell can be used instead of init if we are
* trying to recover a really broken machine .
*/
2005-09-07 02:16:56 +04:00
if ( execute_command ) {
2005-04-17 02:20:36 +04:00
run_init_process ( execute_command ) ;
2005-09-07 02:16:56 +04:00
printk ( KERN_WARNING " Failed to execute %s. Attempting "
" defaults... \n " , execute_command ) ;
}
2005-04-17 02:20:36 +04:00
run_init_process ( " /sbin/init " ) ;
run_init_process ( " /etc/init " ) ;
run_init_process ( " /bin/init " ) ;
run_init_process ( " /bin/sh " ) ;
panic ( " No init found. Try passing init= option to kernel. " ) ;
}