关于printk的分析

前面转了一篇文章，但一直没弄清楚为何printk(linux_banner)会留在log_buf里，今天仔细跟了一下，记录如下，另外还要看一下dmesg...：
printk->vprintk
在函数vprintk
 if (acquire_console_semaphore_for_printk(this_cpu))
  release_console_sem();
在函数static int acquire_console_semaphore_for_printk(unsigned int cpu)中
static int acquire_console_semaphore_for_printk(unsigned int cpu)
{
 int retval = 0;

 if (!try_acquire_console_sem()) {
  retval = 1;

  
  if (!can_use_console(cpu)) {
   console_locked = 0;
   up(&console_sem);
   retval = 0;
  }
 }
 printk_cpu = UINT_MAX;
 spin_unlock(&logbuf_lock);
 return retval;
}
其中的can_use_console
static inline int can_use_console(unsigned int cpu)
{
 return cpu_online(cpu) || have_callable_console();
}
没有console注册，have_callable_console返回0，而cpu_online(cpu)的返回值也要等到kernel_init中调用smp_prepare_cpus函数之后才会为1，所以can_use_console在kernel启动之后一段时间为0，进而acquire_console_semaphore_for_printk返回0，打印就留在log_buf中，

static int __init kernel_init(void * unused)
 smp_prepare_cpus(setup_max_cpus);

void __init smp_prepare_cpus(unsigned int max_cpus)
 current_thread_info()->cpu = 0;