linux-kernel - Re: [PATCH 28/43] x86/mm/kaiser: Map CPU entry area

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]

Date:   Fri, 24 Nov 2017 14:43:40 +0100
From:   Peter Zijlstra <peterz@...radead.org>
To:     Ingo Molnar <mingo@...nel.org>
Cc:     linux-kernel@...r.kernel.org,
        Dave Hansen <dave.hansen@...ux.intel.com>,
        Andy Lutomirski <luto@...capital.net>,
        Thomas Gleixner <tglx@...utronix.de>,
        "H . Peter Anvin" <hpa@...or.com>, Borislav Petkov <bp@...en8.de>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH 28/43] x86/mm/kaiser: Map CPU entry area

On Fri, Nov 24, 2017 at 10:14:33AM +0100, Ingo Molnar wrote:
> + 	/* CPU 0's mapping is done in kaiser_init() */
> +	if (cpu)
> +		kaiser_add_mapping_cpu_entry(cpu);

This hard assumes CPU0 is the boot CPU. I know we dropped Voyager
support a while back, but can/should we hard rely on that?

We do have __boot_cpu_id / get_boot_cpu_id() for these here things.