linux-kernel - Re: [PATCH 01/14] Introduce cpu_enabled

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080715031512.GF14894@parisc-linux.org>
Date:	Mon, 14 Jul 2008 21:15:12 -0600
From:	Matthew Wilcox <matthew@....cx>
To:	Alex Chiang <achiang@...com>
Cc:	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	linux-acpi@...r.kernel.org
Subject: Re: [PATCH 01/14] Introduce cpu_enabled_map and friends

On Mon, Jul 14, 2008 at 08:33:49PM -0600, Alex Chiang wrote:
> Currently, the following cpu maps exist:
> 
> 	cpu_possible_map - map of populatable CPUs
> 	cpu_present_map  - map of populated CPUs
> 	cpu_online_map   - map of schedulable CPUs
> 
> These maps do not provide the concept of populated, but disabled CPUs.
> 
> That is, a system may contain CPU modules that are physically plugged
> in, but disabled by system firmware.

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?

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/