linux-kernel - Re: [PATCH] i386-pda: Initialize the PDA early, before any C code runs.

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <4505F212.4040307@goop.org>
Date:	Mon, 11 Sep 2006 16:32:34 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Andrew Morton <akpm@...l.org>
CC:	Andi Kleen <ak@...e.de>, Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] i386-pda: Initialize the PDA early, before any C code
 runs.

Andrew Morton wrote:
> What is likely to happen if the boot CPU is not CPU #0?  (iirc Voyager does
> that?)
>   

Not sure, but I think this replicates the behaviour of the original code 
(ie, INIT_THREAD_INFO initializes cpu to 0, so smp_processor_id will 
return 0).  Hm, Voyager will probably need a little patch to update the 
the PDA cpu_number properly in smp_setup_processor_id().

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