Skip to content
Snippets Groups Projects
  • Glauber Costa's avatar
    4b5afd0f
    run console earlier · 4b5afd0f
    Glauber Costa authored
    
    We could benefit from the console being ready a bit earlier. The only
    dependency that I see to it are the interrupts that need to be working.  So as
    soon as we initialize the ioapic, we should be able to initialize the console.
    
    This is not the end of story: we still need an even earlier console to debug the
    driver initialization functions, and I was inclined to just leave console_init
    where it is, for now.
    
    But additionally, I felt that loader is really a more appropriate place for
    that than vfs_init... So I propose we switch. In the mean time, it might help
    debug things that happen between ioapic init and the old vfs_init (mem
    initialization, smp bring up, etc)
    
    Signed-off-by: default avatarGlauber Costa <glommer@cloudius-systems.com>
    4b5afd0f
    History
    run console earlier
    Glauber Costa authored
    
    We could benefit from the console being ready a bit earlier. The only
    dependency that I see to it are the interrupts that need to be working.  So as
    soon as we initialize the ioapic, we should be able to initialize the console.
    
    This is not the end of story: we still need an even earlier console to debug the
    driver initialization functions, and I was inclined to just leave console_init
    where it is, for now.
    
    But additionally, I felt that loader is really a more appropriate place for
    that than vfs_init... So I propose we switch. In the mean time, it might help
    debug things that happen between ioapic init and the old vfs_init (mem
    initialization, smp bring up, etc)
    
    Signed-off-by: default avatarGlauber Costa <glommer@cloudius-systems.com>
loader.cc 6.47 KiB