Re: [patch 3/8] x86_64:Dont call enforce_max_cpus when hotplug is enabled

On Mon, Aug 01, 2005 at 01:20:20PM -0700, Ashok Raj wrote:
> No need to enforce_max_cpus when hotplug code is enabled. This
> nukes out cpu_present_map and cpu_possible_map making it impossible to add
> new cpus in the system.

Hmm - i think there was some reason for this early zeroing,
but I cannot remember it right now.

It might be related to some checks later that check max possible cpus.

So it would be still good to have some way to limit max possible cpus.
Maybe with a new option?

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

---

• Follow-Ups:
  • Re: [patch 3/8] x86_64:Dont call enforce_max_cpus when hotplug is enabled
    • From: Ashok Raj <[email protected]>

• References:
  • [patch 0/8] Updated patches for x86_64
    • From: Ashok Raj <[email protected]>
  • [patch 3/8] x86_64:Dont call enforce_max_cpus when hotplug is enabled
    • From: Ashok Raj <[email protected]>

• Prev by Date: Re: [patch 2/8] x86_64: create sysfs entries for cpu only for present cpus
• Next by Date: Re: [patch 4/8] x86_64:Fix cluster mode send_IPI_allbutself to use get_cpu()/put_cpu()
• Previous by thread: [patch 3/8] x86_64:Dont call enforce_max_cpus when hotplug is enabled
• Next by thread: Re: [patch 3/8] x86_64:Dont call enforce_max_cpus when hotplug is enabled
• Index(es):
  • Date
  • Thread

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