Re: [PATCH 01/14] Introduce cpu_enabled_map and friends
- From: Andi Kleen <andi@xxxxxxxxxxxxxx>
- Date: Tue, 15 Jul 2008 12:03:27 +0200
Matthew Wilcox <matthew@xxxxxx> writes:
I don't understand why we want to know about these CPUs. Surely they
should be 'possible', but not 'present'? What useful thing can Linux do
with them?
He explained it in the intro, near the end (I nearly complained about
this too when I hadn't finished reading it completely :):
|The big picture implication is that we can allow userspace
|to interact with disabled CPUs. In this particular example,
|we provide a knob that lets a sysadmin schedule any present
|CPU for firmware deconfiguration or enablement.
The reason sounds pretty exotic, but ok.
-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
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 01/14] Introduce cpu_enabled_map and friends
- From: Russell King
- Re: [PATCH 01/14] Introduce cpu_enabled_map and friends
- References:
- [PATCH 00/14] Introduce cpu_enabled_map and friends
- From: Alex Chiang
- [PATCH 01/14] Introduce cpu_enabled_map and friends
- From: Alex Chiang
- Re: [PATCH 01/14] Introduce cpu_enabled_map and friends
- From: Matthew Wilcox
- [PATCH 00/14] Introduce cpu_enabled_map and friends
- Prev by Date: Re: [GIT *] Allow request_firmware() to be satisfied from in-kernel, use it in more drivers.
- Next by Date: Re: ACPI Error under 2.6.26-rc*
- Previous by thread: Re: [PATCH 01/14] Introduce cpu_enabled_map and friends
- Next by thread: Re: [PATCH 01/14] Introduce cpu_enabled_map and friends
- Index(es):