Re: cpu_up not called for boot cpu

Keith Owens <[email protected]> writes:

> cpu_up() is only called for secondary cpus, not for the boot cpu.  That
> means that code hooked into the cpu_chain notifier never gets called
> for the boot cpu, which prevents additional subsystems from taking
> action for the boot cpu.  So how are additional subsystems meant to be
> initialised for the boot cpu?

They ought to initialize themselves for the already online cpus
when they start.

Any other way would make them lose CPUs if they were loaded
after the other CPUs are added.

-Andi
-
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:
  • cpu_up not called for boot cpu
    • From: Keith Owens <[email protected]>

• Prev by Date: Re: [RFC 1/2] ext3: enlarge blocksize and fix rec_len overflow
• Next by Date: Re: [klibc 04/31] alpha support for klibc
• Previous by thread: Re: cpu_up not called for boot cpu
• Next by thread: How to switch to another process at schedule() ?
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]