lkml.org 
[lkml]   [2017]   [Nov]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [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.

\
 
 \ /
  Last update: 2017-11-24 14:44    [W:0.184 / U:4.892 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site