Re: the creation of boot_cpu_init() is wrong and accessing uninitialised data

Andrew Morton (on Mon, 26 Jun 2006 22:03:37 -0700) wrote:
>It's a bit odd - I think non-zero BSPs happen a bit more often than
>only-on-voyager.

AFAICR, the BSP is supposed to be logical cpu 0 on all architectures.
Most architectures assign logical cpu 0 to the BSP, even if the BSP has
a non-zero hard_smp_processor_id.  ia64 even has this

int __cpu_disable(void)
{
        int cpu = smp_processor_id();

	/*
	 * dont permit boot processor for now
	 */
	if (cpu == 0 && !bsp_remove_ok) {

-
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/

---

• Follow-Ups:
  • Re: the creation of boot_cpu_init() is wrong and accessing uninitialised data
    • From: James Bottomley <[email protected]>

• References:
  • Re: the creation of boot_cpu_init() is wrong and accessing uninitialised data
    • From: Andrew Morton <[email protected]>

• Prev by Date: [PATCH 5/7] bootmem: remove useless headers inclusions
• Next by Date: Re: Incorrect CPU process accounting using CONFIG_HZ=100
• Previous by thread: Re: the creation of boot_cpu_init() is wrong and accessing uninitialised data
• Next by thread: Re: the creation of boot_cpu_init() is wrong and accessing uninitialised data
• 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]