Messages in this thread | | | Date | Fri, 24 Nov 2017 14:43:40 +0100 | From | Peter Zijlstra <> | 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.
| |