linux-kernel - Re: Boot cpu != cpu 0 ?

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Fri, 27 Nov 2009 11:33:50 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	"Nikita V. Youshchenko" <yoush@...msu.su>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Boot cpu != cpu 0 ?

"Nikita V. Youshchenko" <yoush@...msu.su> writes:

> How hard it could be to build a system on multi-core arm hardware, that has 
> linux SMP running in cores other than 0th ?
>
> Say, if bootloader starts kernel on hardware core 1, will kernel be able to 
> work (and use cores 1,2,3 on 4-core hardware) after some tweaking? 
> Or "boot cpu" concept is uncouplable from "hardware core 0" by 
> architecture? 
>
> I'm asking because there is a project with a strict requerement to have 
> core 0 reserved and not touched by linux, and I need to understand how 
> realistic it is.

You need to be clear what CPU 0 means. It could be "Linux CPU
number 0" That will be always there (it's hard coded), but that's
really only a numbering convention inside a kernel that essentially
says "nth booted CPU"

Then there's the APIC ID, which is the number the CPU hardware
knows about. There's a APIC ID == 0. Linux does not rely
on CPU #0 having APIC ID 0, at least not in principle
(this has regressed occasionally in the past)

The larger problem with sharing cores like this is the memory map --
e.g. you would need to coordinate which kernels owns which hardware
and which memory, which is not trivial without help. The usual way to
do this is to use a VM.

-Andi
-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/